On 01/16/2013 04:00 PM, Michael Weber wrote: > On 01/16/2013 06:33 PM, Michael Orlitzky wrote: >> Yes, sorry for the confusion. I use more than one package manager, >> and when doing an "update" or "upgrade" I'm basically flipping a >> coin. > hehe, as long as we don't --dist-upgrade ;-) > the g was intentional. > > how does portage @preserved-libs work?
@preserved-rebuild is a package set, which is intended to be obsoleted by EAPI 5 slot-operator automatic rebuilds, as I've mentioned in this blog post: http://blogs.gentoo.org/zmedico/2012/09/21/preserve-libs-available-in-portage-2-1/ > maybe we could emerge @update[s] The @ symbol is reserved for package sets, which expand to a set of atoms that are used to select a specific set of packages. Package sets are intended to be orthogonal emerge options. > @glsa. In portage-2.2 we have the @security package set, which generates atoms from the intersection of the glsa database with your installed packages. The @security code has not been kept in sync with glsa-check (from gentoolkit), so it may contain bugs that have already been fixed in glsa-check. -- Thanks, Zac
