public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joe Peterson <lavajoe@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New PDEPEND behaviour.
Date: Wed, 25 Jul 2007 08:31:41 -0600	[thread overview]
Message-ID: <46A75ECD.2090404@gentoo.org> (raw)
In-Reply-To: <200707251408.41171.peper@gentoo.org>

Piotr Jaroszyński wrote:
> We need to update docs or harass zmedico to force PDEPEND to be pulled as soon 
> as possible but not before the pkg that pulls it.

There is another problem with PDEPEND that I've run into: if you are
doing an emerge that fails some time after the package containing the
PDEPEND builds but *before* the depended-on package builds successfully,
the dependency will not be "remembered" as needed on the next emerge
(unless you do a resume, of course).  So, basically, the dependency gets
forgotten.  The new behavior discussed here makes this scenario less
likely but does not eliminate it.

						-Joe


-- 
gentoo-dev@gentoo.org mailing list



      parent reply	other threads:[~2007-07-25 14:37 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-25 12:08 [gentoo-dev] New PDEPEND behaviour Piotr Jaroszyński
2007-07-25 12:32 ` Brian Harring
2007-07-25 12:46 ` Doug Goldstein
2007-07-25 14:15   ` Ciaran McCreesh
2007-07-25 14:24     ` Doug Goldstein
2007-07-25 14:32       ` Ciaran McCreesh
2007-07-25 12:51 ` Carsten Lohrke
2007-07-25 14:17   ` Ciaran McCreesh
2007-07-25 14:28     ` Doug Goldstein
2007-07-25 14:41       ` Ciaran McCreesh
2007-07-25 14:25   ` Brian Harring
2007-07-25 15:17     ` Carsten Lohrke
2007-07-25 15:32       ` Vlastimil Babka
2007-07-25 17:31         ` Carsten Lohrke
2007-07-25 14:18 ` Ciaran McCreesh
2007-07-25 15:18   ` Piotr Jaroszyński
2007-07-25 14:18 ` Doug Goldstein
2007-07-25 14:31   ` Ciaran McCreesh
2007-07-25 15:07   ` Piotr Jaroszyński
2007-07-25 14:31 ` Joe Peterson [this message]

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=46A75ECD.2090404@gentoo.org \
    --to=lavajoe@gentoo.org \
    --cc=gentoo-dev@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