summaryrefslogtreecommitdiffstats
path: root/pym/_emerge/actions.py
diff options
context:
space:
mode:
authorZac Medico <zmedico@gentoo.org>2009-10-18 21:06:39 +0000
committerZac Medico <zmedico@gentoo.org>2009-10-18 21:06:39 +0000
commit84de8f714de5d4599c5ea8dd207ed237b6a3c883 (patch)
tree41404165dd7766cdc327555412cef867de0e676d /pym/_emerge/actions.py
parentf2e3f317c18b82175c91b86b29fe1b253811faec (diff)
downloadportage-84de8f714de5d4599c5ea8dd207ed237b6a3c883.tar.gz
portage-84de8f714de5d4599c5ea8dd207ed237b6a3c883.tar.bz2
portage-84de8f714de5d4599c5ea8dd207ed237b6a3c883.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. svn path=/main/trunk/; revision=14679
Diffstat (limited to 'pym/_emerge/actions.py')
0 files changed, 0 insertions, 0 deletions