Daniel da Veiga wrote:
> 
> I'll just quote the "emerge" man page, that is pretty clear there:
> 
--snip
> 
> Note the words "DIRECT dependencies". So, your command "emerge
> --update --deep world" is in fact just "emerge world", because every
> direct/indirect dependency is part of your world file. Your "way" made
> "--update" useless, because a simple "emerge <package>" would update
> the package.
> 

--snip

> So, you "way" also made "--deep" useless.
> This flags are there because they mantain portage in a way that you
> can't easily break consistency by accident, and with that I mean
> libraries and indirect dependencies.

Yes, and I'll ask again what's the point of doing:

"emerge world" or "emerge --update world"?

If one doesn't use "--deep" not all the packages get updated. Thats what
bothers me. Later on this mail you say that even you make "emerge -iDN
world" on a daily basis.


--snip

> Also, the world file is a simple way to keep a package version (by
> removing it from world), for instance, I don't wanna upgrade mysql
> with my nightly "emerge -uDN world", so, its not in my world file.
> 

Nothing prevents me of doing the same thing, right? ;-)

> Also note that "indirect" dependencies can be a pain, and packages may
> depend on a LOT of other packages, if you want an example, check
> "emerge -euDt links -pv". You can check indirect dependencies! I just
> say there are quite a few, and portage knows how to deal with all this
> stuff (at least never proved me wrong).
> 

Yes, and putting almost all of the packages in the world list does not
prevent portage of doing its job.

So who and why would use "emerge world" and "emerge --update world" ?

-- 
Best regards,
Daniel

-- 
gentoo-user@gentoo.org mailing list

Reply via email to