public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] pkg_nofetch: $A vs. $SRC_URI
Date: Tue, 4 Jul 2006 15:32:47 -0400	[thread overview]
Message-ID: <200607041532.47374.vapier@gentoo.org> (raw)
In-Reply-To: <200607041445.29915.vapier@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 736 bytes --]

On Tuesday 04 July 2006 14:45, Mike Frysinger wrote:
> On Monday 03 July 2006 21:00, Robin H. Johnson wrote:
> > If you have an ebuild with a non-standard pkg_nofetch, please ensure
> > that you use $SRC_URI instead of $A!
> >
> > This is because if you have FEATURES=mirror or FEATURES=cvs, attempts to
> > download all of the source files for digesting or verification will hit
> > pkg_nofetch and $A is only the subset of $SRC_URI, causing misleading
> > messages to be displayed about what needs to be downloaded still.
>
> whats the problem then ?

sorry, i just re-read your message ... perhaps a better fix would be to not 
force people to download all the packages when something has fetch 
restrictions ?
-mike

[-- Attachment #2: Type: application/pgp-signature, Size: 827 bytes --]

  reply	other threads:[~2006-07-04 19:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-04  1:00 [gentoo-dev] pkg_nofetch: $A vs. $SRC_URI Robin H. Johnson
2006-07-04  2:13 ` Donnie Berkholz
2006-07-04  2:36   ` Robin H. Johnson
2006-07-04 18:59     ` Donnie Berkholz
2006-07-04 19:35     ` Zac Medico
2006-07-04 20:08       ` Robin H. Johnson
2006-07-05  9:29       ` Marius Mauch
2006-07-05 18:10         ` Zac Medico
2006-07-05 17:48           ` Marius Mauch
2006-07-04 18:45 ` Mike Frysinger
2006-07-04 19:32   ` Mike Frysinger [this message]
2006-07-04 20:10     ` Robin H. Johnson
2006-07-04 20:56       ` Mike Frysinger

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=200607041532.47374.vapier@gentoo.org \
    --to=vapier@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