On Sunday 24 May 2009 20:06:59 Arttu V. wrote: > On 5/24/09, Alan McKinnon <alan.mckin...@gmail.com> wrote: > > profiles are cascading and support multiple inheritance (parent files can > > contain several entries). So, you have to run > > > > find /usr/portage/profiles -name packages > > > > to find them all, and apply brain power to find the few that actually > > apply > > Cascading yes, but I'd say no to the find-command. You should be able > to ask portage itself. After all, it has to know your current system > set for its own work, let it do the cascading calculations (unions for > sets):
Dale asked *where* system is defined, not what it consists of. These are entirely different questions with entirely different answers. > emerge -p @system > > And even better, if I read correctly from portage man-page (look for > the "packages" and packages.build file section there), it is nearly > trivial to add files to a local system set. Just add > asterisk-prepended lines to /etc/portage/profile/packages. Just tried > it, it seems to work, got python and games-board/megamek added to my > system set according to emerge -p @system! :D It appears you are completely missing the point. It is indeed very easy to add things to the @system set, but we are talking about the system set, and it is broken out of the box as shipped. Look at the size of this thread already and what it has taken to gain the understanding we have now. How is a new user supposed to be able to figure this out? Portage will not let you unmerge portage or gcc without a fight. It offers a way to back up these critical packages. No rational person will attempt to argue that python in a *portage* system is not subject to the same constraints. But it's not working that way today. Ergo, it is broken. -- alan dot mckinnon at gmail dot com
