| Summary: | app-containers/docker-compose-2.x: version bump | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Sam James <sam> |
| Component: | Current packages | Assignee: | William Hubbs <williamh> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | hydrapolic, sping |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: | https://bugs.gentoo.org/show_bug.cgi?id=804867 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Sam James
2022-03-10 03:59:18 UTC
That would rock, thanks in advance! *** Bug 804867 has been marked as a duplicate of this bug. *** @sping: Do you suggest slotting this or should I replace docker-compose-1.x on systems? (In reply to William Hubbs from comment #3) > @sping: > Do you suggest slotting this or should I replace docker-compose-1.x on > systems? I'd prefer slotting. The bug and feature set are not identical, e.g. I know of some setups that 2.x cannot handle that 1.x can. Would that work for you? There is some chance the resulting file set is even free of overlaps, e.g. I think the binary location is different. Maybe you can have both slots installed in parallel even without much of a cost to the ebuild. I think you are right about 1.x and 2.x being installed at the same time with no issues, so I'll take a look at slotting. Cool, thank you! The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=32b399df99a600dfc343a1d4ff72c10c2d6d1982 commit 32b399df99a600dfc343a1d4ff72c10c2d6d1982 Author: William Hubbs <williamh@gentoo.org> AuthorDate: 2022-03-15 17:19:37 +0000 Commit: William Hubbs <williamh@gentoo.org> CommitDate: 2022-03-15 17:24:22 +0000 app-containers/docker-compose: add 2.3.3 Closes: https://bugs.gentoo.org/834872 Signed-off-by: William Hubbs <williamh@gentoo.org> app-containers/docker-compose/Manifest | 2 + .../docker-compose/docker-compose-2.3.3.ebuild | 48 ++++++++++++++++++++++ 2 files changed, 50 insertions(+) Thank you @William! |