From: Daniel Iliev <danny@ilievnet.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] world favorites: pros and cons
Date: Wed, 05 Jul 2006 23:01:02 +0300 [thread overview]
Message-ID: <44AC1A7E.5040401@ilievnet.com> (raw)
In-Reply-To: <342e1090607051217w6fabbefegb8883650b5166e38@mail.gmail.com>
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
next prev parent reply other threads:[~2006-07-05 20:15 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-05 9:48 [gentoo-user] world favorites: pros and cons Daniel
2006-07-05 10:10 ` Neil Bothwick
2006-07-05 10:21 ` Alexander Skwar
2006-07-05 10:18 ` Alexander Skwar
2006-07-05 10:55 ` Neil Bothwick
2006-07-05 11:11 ` Daniel
2006-07-05 11:33 ` Rumen Yotov
2006-07-05 11:54 ` Daniel Iliev
2006-07-05 12:14 ` Neil Bothwick
2006-07-05 12:43 ` Daniel Iliev
2006-07-05 13:16 ` Alexander Skwar
2006-07-05 14:47 ` Alan McKinnon
2006-07-05 13:21 ` Neil Bothwick
2006-07-05 14:29 ` Daniel Iliev
2006-07-05 15:08 ` Neil Bothwick
2006-07-05 16:53 ` Daniel Iliev
2006-07-05 20:15 ` Neil Bothwick
2006-07-05 16:38 ` Richard Fish
2006-07-05 17:10 ` Daniel Iliev
2006-07-05 18:15 ` Richard Fish
2006-07-05 18:59 ` Daniel Iliev
2006-07-05 19:47 ` Richard Fish
2006-07-05 16:54 ` Daniel da Veiga
2006-07-05 18:30 ` Daniel Iliev
2006-07-05 19:17 ` Daniel da Veiga
2006-07-05 20:01 ` Daniel Iliev [this message]
2006-07-28 18:30 ` Enrico Weigelt
2006-07-28 18:46 ` [gentoo-user] " Jim Ramsay
2006-07-28 18:57 ` Alexander Skwar
2006-07-28 19:10 ` Enrico Weigelt
2006-07-28 19:30 ` Jim Ramsay
2006-07-28 20:39 ` Daniel da Veiga
2006-07-28 21:03 ` Jim Ramsay
2006-07-28 21:03 ` Jim Ramsay
2006-08-07 16:53 ` Enrico Weigelt
2006-07-05 22:27 ` [gentoo-user] " Daniel Iliev
2006-07-05 22:43 ` Ryan Tandy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44AC1A7E.5040401@ilievnet.com \
--to=danny@ilievnet.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox