public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
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 20:10:13 +0300	[thread overview]
Message-ID: <44ABF275.3040107@ilievnet.com> (raw)
In-Reply-To: <7573e9640607050938t31b5b0edmf9a2a672ed017ba0@mail.gmail.com>

Richard Fish wrote:

> If you later take X out of your use flags, and do an emerge -DNuv
> world, the A no longer depends on B.  But since it is still in your
> world file, portage will assume you want this package, and continue to
> compile updates for it with each new version.  That can be a pretty
> huge waste of time.

Thanks! Good point!


--snip
>  Why not just merge the
> top-level package, and if you don't like it, unmerge and use
> --depclean --pretend to figure out what can safely be removed?
> 

Because if I decide to keep it, all dependencies it pulls-in don't get
updated until the top-level package starts depending on a different
version of those packages. Actually this is the main reason I started
this practice.
"emerge --depclean" yells a big warning that it is broken.

> And I don't necessarily believe that having everything in world
> results in a significantly faster scan time than having only top-level
> packages there.  I would like to see actual proof of this assertion.
> 
> -Richard

No, no! I'm saying just the opposite - the more packages you have
recorded in the world list, the slower scanning you get.


-- 
Best regards,
Daniel

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-07-05 17:47 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 [this message]
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
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=44ABF275.3040107@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