1 |
On Monday 05 September 2005 04:07, Philip Webb wrote: |
2 |
> 050904 Andrew Gaffney wrote: |
3 |
> > Philip Webb wrote: |
4 |
> >> I actually have |
5 |
> >> /etc/make.profile -> /usr/portage/profiles/default-linux/x86/2005.1 |
6 |
> >> So when I enter 'emerge -Cp devfsd', why do I get : |
7 |
> >> "!!! Trying to unmerge package(s) in system profile. 'sys-fs/devfsd' |
8 |
> >> !!! This could be damaging to your system" |
9 |
> > |
10 |
> > Most likely, you're seeing this because the 'system' target contains |
11 |
> > 'virtual/dev-manager' (defined in /usr/portage/profiles/base/). |
12 |
> > devfsd satisfies this dependency (as well as udev). |
13 |
> > Portage apparently isn't smart enough to notice |
14 |
> > that there's another package installed that satisfies this dependency. |
15 |
> > You can safely unmerge devfsd if you have udev installed and working. |
16 |
> |
17 |
> Yes, someone provided a very clear explanation to my parallel query |
18 |
> & yes, Devfsd's ebuild does have a similar 'PROVIDE' line to Joe's. |
19 |
> |
20 |
> As you say, Portage lacks intelligence here: |
21 |
> it needs to be educated to check for other packages |
22 |
> or in the meantime make a less forthright warning. |
23 |
> |
24 |
> Thanx for your explanation, which is what I really wanted. |
25 |
|
26 |
Not always possible. If you have two gccs installed and decide to unmerge |
27 |
one of them, it is completely possible that it'd break half of your system. |
28 |
|
29 |
-- |
30 |
Jason Stubbs |