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