Mark Knecht wrote:
On Sun, Jan 1, 2012 at 2:31 PM, Dale<[email protected]> wrote:
Michael Orlitzky wrote:
On 01/01/2012 05:06 PM, Michael Mol wrote:
On Sun, Jan 1, 2012 at 4:50 PM, Michael Orlitzky<[email protected]>
wrote:
Using "emerge --update foo" adds "foo" to your world file. This is
responsible for pretty much every package that incorrectly found its way
into one of my world files.
Is there any reason to desire the current behavior? I'd like to suggest
that
it be fixed, but want to be sure I'm not just being short-sighted.
Pretty sure that's what -1 is for. I'm just getting the hang of it
myself.
Well, I know what I'm *supposed* to do. My complaint is basically that I
sometimes forget to add -1 with -u, and that bad things happen as a result.
But why should I have to add -1 along with it? Is there any reason you
would ever want -u to add a package to your world file? If not, we can avoid
headaches in the future by making it do the sane (not harmful) thing.
Using -u used to work the way you describe but that was a while ago. The
only thing I know of is to add --oneshot to make.conf so you don't forget.
I think they knew this was going to be a issue. This is in man emerge:
--select [ y | n ]
Add specified packages to the world set (inverse of --oneshot). This is
useful if you want to use EMERGE_DEFAULT_OPTS to make --oneshot behavior
default.
The way I read that is that they expect you to add --oneshot to make.conf.
Like you, this makes no sense to me. I would rather they leave it the way
it was and then not needed the --select option at all. :/
Then again, they add confusion so we can fix it in make.conf. lol
Dale
:-) :-)
--
I am only responsible for what I said ... Not for what you understood or how
you interpreted my words!
Miss the compile output? Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"
I'm not clear. Why does one ever bother with emerge -u package? In 10
years of Gentoo I've managed to get by with basically either emerge
package to add something or emerge -DuN @world to stay updated. (or
@system in the old days but no longer...)
Not picking on anyone but in my mind emerge -u package _should_ add
the package to the world file because any time I run emerge with a
package name and without -1 I'm telling it to make it part of @world.
If it's not part of @world, and is already on the machine, then emerge
-DuN @world is the right way to get it and everything else updated.
Just curious...
- Mark
Sometimes I do my updates one package at a time. I would then use the
-u option so that it would be updated, not added to world. To me,
update means update. If there is no option then it should be installed
and added to world. That is how it was done for a good long while then
got changed.
Dale
:-) :-)
--
I am only responsible for what I said ... Not for what you understood or how
you interpreted my words!
Miss the compile output? Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"
