public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Frank Peters <frank.peters@comcast.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] Re: Portage Fails To Find Updates
Date: Mon, 14 Dec 2009 13:01:32 -0500	[thread overview]
Message-ID: <20091214130132.193d6c98.frank.peters@comcast.net> (raw)
In-Reply-To: <20091214124309.fb40ca6e.frank.peters@comcast.net>

On Mon, 14 Dec 2009 12:43:09 -0500
Frank Peters <frank.peters@comcast.net> wrote:

> 
> Why has portage failed to add all packages to the "world" file?
> Have I been doing something wrong?
> 

Well, I found the answer to my own question.  From the portage man
page:

 "Every  time  you  emerge  a package, the package that you
requested is recorded here.  Then when  you  run  `emerge
world  -up`, the list of packages is read from this file.
Note that this does not mean that the packages that  were
installed  as dependencies are listed here.  For example,
if you run `emerge mod_php` and you do  not  have  apache
already,  then "dev-php/mod_php" is recorded in the world
file but "net-www/apache" is not."

But to use the example of the package rpm2targz, using the command
"equery depends rpm2targz" I discover that media-fonts/urw-fonts-2.4.6
is the only package that depends on rpm2targz.  Thus, when I installed
urw-fonts, rpm2targz must have also been installed but not listed 
in the "world" file.

However, this practice seems to be a bad idea.  Since the time that I
installed urw-fonts, the package rpm2targz has been updated but I will
never know this unless urw-fonts also becomes updated.  A similar situation
could exist for many other packages.  Portage should by default enter all
packages into the "world" file.

Frank Peters



  reply	other threads:[~2009-12-14 20:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-14 17:43 [gentoo-amd64] Portage Fails To Find Updates Frank Peters
2009-12-14 18:01 ` Frank Peters [this message]
2009-12-14 20:21   ` [gentoo-amd64] " Barry Schwartz
2009-12-14 18:55 ` Nikos Chantziaras
2009-12-14 19:39 ` [gentoo-amd64] " Morgan Wesström

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=20091214130132.193d6c98.frank.peters@comcast.net \
    --to=frank.peters@comcast.net \
    --cc=gentoo-amd64@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