summaryrefslogtreecommitdiffstats
path: root/pym/_emerge/depgraph.py
diff options
context:
space:
mode:
authorZac Medico <zmedico@gentoo.org>2009-10-19 03:43:21 +0000
committerZac Medico <zmedico@gentoo.org>2009-10-19 03:43:21 +0000
commitfd52521ee932a9e71e432a23cd31920e190b8e81 (patch)
treeab7e65937d2a6819f17547f4860dcba55e3021fa /pym/_emerge/depgraph.py
parent9db8ae39f12ee9ef51019d4bdf3d51719ce4f643 (diff)
downloadportage-fd52521ee932a9e71e432a23cd31920e190b8e81.tar.gz
portage-fd52521ee932a9e71e432a23cd31920e190b8e81.tar.bz2
portage-fd52521ee932a9e71e432a23cd31920e190b8e81.zip
Remove support for 'extend', 'remove', and 'intersect' sets.conf section
attributes in SetConfig.getSetAtoms() since the current implementation does not meet user expectations, as mentioned in bug #253802, comment #5: Package set operators currently operate on atoms, but what users really need is for them to operate on the packages themselves. This will allow one set to add or subtract packages from another even though the sets to not use the exact same atoms to refer to the given packages. I imagine the way this should be done is to create a mapping of atom -> package for each set, perform the intersection using the packages, and then map the package intersection back into a set of atoms. (trunk r14679) svn path=/main/branches/2.1.7/; revision=14690
Diffstat (limited to 'pym/_emerge/depgraph.py')
0 files changed, 0 insertions, 0 deletions