1 |
I didn't know the emaint command, but I tried it and it didn't work. |
2 |
It still wants to remove gcc-3 even though I need that for qemu-softmmu. |
3 |
|
4 |
So I guess I need to use the -n to add everything manual to my world file.... |
5 |
|
6 |
On Mon, Nov 24, 2008 at 12:27 PM, ABCD <en.ABCD@×××××.com> wrote: |
7 |
> -----BEGIN PGP SIGNED MESSAGE----- |
8 |
> Hash: SHA1 |
9 |
> |
10 |
> Duncan wrote: |
11 |
>> Try emerge with the -n/--noreplace option, which is sort of the reverse |
12 |
>> of -1/--oneshot (and not to be confused with -N/--newuse). If the |
13 |
>> package is already merged, -n just adds it to the world file without |
14 |
>> actually remerging it. Then --depclean won't try to remove it or its |
15 |
>> dependencies. |
16 |
>> |
17 |
>> I do this all the time since I use --oneshot in my (stub-scripted) normal |
18 |
>> emerge commands. Unless I know I want to keep it (in which case I use a |
19 |
>> special version without the --oneshot), I'll use a script that adds -1 by |
20 |
>> default. That way I can try out a package and decide if I like it, |
21 |
>> before either adding it to world using emerge -n or --depcleaning it and |
22 |
>> dependencies. Then, since I always use -a or -p as well, when I run |
23 |
>> --depclean I'll get a list of packages I haven't decided on yet. I |
24 |
>> seldom run --depclean and let it do its thing, preferring to use emerge |
25 |
>> -C to unmerge packages on the list specifically, if I've decided not to |
26 |
>> keep them, or emerge -n to add them to my world file if I do want to keep |
27 |
>> them. If I've not decided yet, they just sit in the list, but that |
28 |
>> doesn't happen very long for very many packages, and my --depclean -p |
29 |
>> list is usually empty. |
30 |
> |
31 |
> I do something similar, but I (almost) never use emerge -C, instead, to |
32 |
> remove a package, I use emerge --depclean category/package, which |
33 |
> removes a package *only if* it is not a dependency of something else (I |
34 |
> only use -C/--unmerge when I know that it isn't a dep, but portage |
35 |
> thinks it is (eg, "|| ( foo/bar foo/baz )", when I have both foo/bar and |
36 |
> foo/baz installed, portage won't remove either with --depclean in some |
37 |
> cases). |
38 |
> |
39 |
>> Also note the --with-bdeps=<y|n> option. Since I always want build |
40 |
>> dependencies retained, I have EMERGE_DEFAULT_OPTIONS="--with-bdeps=y" set |
41 |
>> (along with --keep-going and --nospinner, but the bdeps option is what is |
42 |
>> important here). Otherwise, --depclean will always want to unmerge build |
43 |
>> dependencies as they aren't needed to actually run the package, only to |
44 |
>> build it. |
45 |
> |
46 |
> Actually, --with-bdeps=y is the default when you use --depclean, exactly |
47 |
> for that reason. |
48 |
> |
49 |
> - -- |
50 |
> ABCD |
51 |
> -----BEGIN PGP SIGNATURE----- |
52 |
> Version: GnuPG v2.0.9 (GNU/Linux) |
53 |
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
54 |
> |
55 |
> iEYEARECAAYFAkkqj7AACgkQOypDUo0oQOqWBACdG7ZUaelv4QeQCFA/AAH8plcR |
56 |
> fSIAmQGap/c4dCisRX4Vo6YvAyQgMyd8 |
57 |
> =uRM/ |
58 |
> -----END PGP SIGNATURE----- |
59 |
> |
60 |
> |
61 |
> |
62 |
|
63 |
|
64 |
|
65 |
-- |
66 |
Tonko |