Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 496844 - portage: implement exclusion of packages and sets in nested sets
Summary: portage: implement exclusion of packages and sets in nested sets
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Enhancement/Feature Requests (show other bugs)
Hardware: All All
: Normal normal (vote)
Assignee: Portage team
Depends on:
Reported: 2014-01-03 08:28 UTC by Jaak Ristioja
Modified: 2014-01-04 13:09 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Jaak Ristioja 2014-01-03 08:28:32 UTC
I suggest the following syntax be allowed for set files:


The semantics for this are straightforward: include all of @kde except the packages in @kdegames and kde-base/ksystemlog.

Currently stuff like this yields the such kind of errors from portage:

  /etc/portage/sets/mykde: Validation failed at line: 2, data -@kdegames

However, the following probably doesn't make sense:


I think this enhancement would be most appreciated by some users (e.g. bug 182106 about kde*-meta ebuilds).

PS: I just discovered user set support a few minutes ago, so please excuse me, if I don't fully understand it yet.
PPS: It's strange that circularly nested sets seem to be currently allowed:



# emerge @test --nodeps -pq
[ebuild   R   ] kde-base/kmines-4.12.0
[ebuild   R   ] kde-base/kwrite-4.12.0
# emerge @test2 --nodeps -pq
[ebuild   R   ] kde-base/kwrite-4.12.0
[ebuild   R   ] kde-base/kmines-4.12.0

I'm not sure what the semantics of the !atom syntax for set files should be in this case.