From: "Daniel da Veiga" <danieldaveiga@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] world favorites: pros and cons
Date: Wed, 5 Jul 2006 13:54:55 -0300 [thread overview]
Message-ID: <342e1090607050954w3f3c12a3o47a26bab72802338@mail.gmail.com> (raw)
In-Reply-To: <44ABB409.4080003@ilievnet.com>
On 7/5/06, Daniel Iliev <danny@ilievnet.com> wrote:
> Neil Bothwick wrote:
> >
> > Now portage has no idea of which packages
> > are there because you want them, which are there because they are
> > dependencies of something you want and which are redundant cruft installed
> > as a dependency of a package you no longer have installed.
> >
> > On your system, your packages, their dependencies and the cruft are all
> > considered part of world.
> >
> >
>
> That is correct. What are the disadvantages besides the longer seeks for
> updates?
>
> I have no problem with the redundant cruft - when I want just to try
> some package I do "emerge --pretend" and record the list of dependencies
> it wants to pull-in. If I decide the package is not useful to me, I
> "un-emerge" not only the package, but also the dependencies it had
> pulled-in during its installation.
>
>
You're manually doying stuff that portage should do. This breaks
portage system, gives you more trouble (because you have to manually
"undo" stuff in order to not break your dependency list) and have
turned the whole dependency check lists and ebuils dependency check
useless. A "emerge --update --deep world" for you is a "emerge world".
You put some of the work of portage on your own hands, don't be
surprised if that breaks something.
--
Daniel da Veiga
Computer Operator - RS - Brazil
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V-
PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++
------END GEEK CODE BLOCK------
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-07-05 17:48 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 [this message]
2006-07-05 18:30 ` Daniel Iliev
2006-07-05 19:17 ` Daniel da Veiga
2006-07-05 20:01 ` Daniel Iliev
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=342e1090607050954w3f3c12a3o47a26bab72802338@mail.gmail.com \
--to=danieldaveiga@gmail.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