Zac Medico schrieb:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marius Mauch wrote:
Zac Medico schrieb:
If a version of SRC_URI that has all the conditionals evaluated is
needed in the ebuild environment, then I think we should use a new
variable name. Otherwise, it's ambiguous.
Doesn't $A
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marius Mauch wrote:
> Zac Medico schrieb:
>> If a version of SRC_URI that has all the conditionals evaluated is
>> needed in the ebuild environment, then I think we should use a new
>> variable name. Otherwise, it's ambiguous.
>
> Doesn't $AA already
Zac Medico schrieb:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robin H. Johnson wrote:
When FEATURES=mirror, and you try to fetch, it does indeed contain unevaluated
USE flags. However for FEATURES=-mirror, the content of it is correct - no USE
flags at all.
Are you sure about the SRC_URI
On Tuesday 04 July 2006 16:10, Robin H. Johnson wrote:
> On Tue, Jul 04, 2006 at 03:32:47PM -0400, Mike Frysinger wrote:
> > 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 ?
>
> That
On Tue, Jul 04, 2006 at 03:32:47PM -0400, Mike Frysinger wrote:
> 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 ?
That's not an option if you are re-digesting the package (FEATURES=cv
On Tue, Jul 04, 2006 at 12:35:04PM -0700, Zac Medico wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Robin H. Johnson wrote:
> > When FEATURES=mirror, and you try to fetch, it does indeed contain
> > unevaluated
> > USE flags. However for FEATURES=-mirror, the content of it is correc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robin H. Johnson wrote:
> When FEATURES=mirror, and you try to fetch, it does indeed contain unevaluated
> USE flags. However for FEATURES=-mirror, the content of it is correct - no USE
> flags at all.
Are you sure about the SRC_URI being different?
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, attempt
Robin H. Johnson wrote:
> When FEATURES=mirror, and you try to fetch, it does indeed contain unevaluated
> USE flags. However for FEATURES=-mirror, the content of it is correct - no USE
> flags at all.
>
> Maybe a two-part solution is in order here then:
> 1. Change portage behavior regarding the
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 verifi
On Mon, Jul 03, 2006 at 07:13:35PM -0700, Donnie Berkholz wrote:
> 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
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
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_U
13 matches
Mail list logo
