The amd64 arch profile package.use.stable.mask contains the following: # Mikle Kolyada <zlogene@gentoo.org> (14 Jun 2015) # app-emulation/lxc has no stable versions app-emulation/docker lxc However, =app-emulation/lxc-1.0.7 was also marked stable on amd64 on the same date, which seems to indicate the opposite of this mask. As far as I can tell, this mask makes it impossible to emerge stable app-emulation/docker with lxc support. Reproducible: Always Steps to Reproduce: USE=lxc emerge -pv app-emulation/docker Actual Results: These are the packages that would be merged, in order: [ebuild R ] app-emulation/docker-1.7.1::gentoo USE="contrib overlay (-apparmor) -aufs -btrfs -device-mapper -doc -experimental (-lxc) -vim-syntax" 0 KiB Expected Results: These are the packages that would be merged, in order: [ebuild R ] app-emulation/docker-1.7.1::gentoo USE="contrib lxc overlay (-apparmor) -aufs -btrfs -device-mapper -doc -experimental -vim-syntax" 0 KiB
Given that upstream is going to deprecate LXC support entirely soon (https://github.com/docker/docker/pull/15255), would it make sense to just remove the flag entirely now, or wait until upstream really does drop support for it?
I'd say it's fine to remove on a bump once it's deprecated upstream. Makes sense to keep it in line with the upstream support as much as possible. Just my 2¢.
Last version supporting lxc was removed per bug 581236
