1 |
On Sun, Jan 1, 2012 at 2:31 PM, Dale <rdalek1967@×××××.com> wrote: |
2 |
> Michael Orlitzky wrote: |
3 |
>> |
4 |
>> On 01/01/2012 05:06 PM, Michael Mol wrote: |
5 |
>>> |
6 |
>>> On Sun, Jan 1, 2012 at 4:50 PM, Michael Orlitzky<michael@××××××××.com> |
7 |
>>> wrote: |
8 |
>>>> |
9 |
>>>> Using "emerge --update foo" adds "foo" to your world file. This is |
10 |
>>>> responsible for pretty much every package that incorrectly found its way |
11 |
>>>> into one of my world files. |
12 |
>>>> |
13 |
>>>> Is there any reason to desire the current behavior? I'd like to suggest |
14 |
>>>> that |
15 |
>>>> it be fixed, but want to be sure I'm not just being short-sighted. |
16 |
>>> |
17 |
>>> |
18 |
>>> Pretty sure that's what -1 is for. I'm just getting the hang of it |
19 |
>>> myself. |
20 |
>>> |
21 |
>>> |
22 |
>> |
23 |
>> Well, I know what I'm *supposed* to do. My complaint is basically that I |
24 |
>> sometimes forget to add -1 with -u, and that bad things happen as a result. |
25 |
>> |
26 |
>> But why should I have to add -1 along with it? Is there any reason you |
27 |
>> would ever want -u to add a package to your world file? If not, we can avoid |
28 |
>> headaches in the future by making it do the sane (not harmful) thing. |
29 |
>> |
30 |
>> |
31 |
> |
32 |
> Using -u used to work the way you describe but that was a while ago. The |
33 |
> only thing I know of is to add --oneshot to make.conf so you don't forget. |
34 |
> I think they knew this was going to be a issue. This is in man emerge: |
35 |
> |
36 |
> --select [ y | n ] |
37 |
> Add specified packages to the world set (inverse of --oneshot). This is |
38 |
> useful if you want to use EMERGE_DEFAULT_OPTS to make --oneshot behavior |
39 |
> default. |
40 |
> |
41 |
> The way I read that is that they expect you to add --oneshot to make.conf. |
42 |
> Like you, this makes no sense to me. I would rather they leave it the way |
43 |
> it was and then not needed the --select option at all. :/ |
44 |
> |
45 |
> Then again, they add confusion so we can fix it in make.conf. lol |
46 |
> |
47 |
> |
48 |
> Dale |
49 |
> |
50 |
> :-) :-) |
51 |
> |
52 |
> -- |
53 |
> I am only responsible for what I said ... Not for what you understood or how |
54 |
> you interpreted my words! |
55 |
> |
56 |
> Miss the compile output? Hint: |
57 |
> EMERGE_DEFAULT_OPTS="--quiet-build=n" |
58 |
> |
59 |
> |
60 |
|
61 |
I'm not clear. Why does one ever bother with emerge -u package? In 10 |
62 |
years of Gentoo I've managed to get by with basically either emerge |
63 |
package to add something or emerge -DuN @world to stay updated. (or |
64 |
@system in the old days but no longer...) |
65 |
|
66 |
Not picking on anyone but in my mind emerge -u package _should_ add |
67 |
the package to the world file because any time I run emerge with a |
68 |
package name and without -1 I'm telling it to make it part of @world. |
69 |
If it's not part of @world, and is already on the machine, then emerge |
70 |
-DuN @world is the right way to get it and everything else updated. |
71 |
|
72 |
Just curious... |
73 |
|
74 |
- Mark |