From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] SRC_URI behaviour
Date: Sat, 15 Jun 2013 17:35:02 +0100 [thread overview]
Message-ID: <20130615173502.0fc279a9@googlemail.com> (raw)
In-Reply-To: <51BC2C55.7010506@mva.name>
[-- Attachment #1: Type: text/plain, Size: 1375 bytes --]
On Sat, 15 Jun 2013 15:56:53 +0700
"Vadim A. Misbakh-Soloviov" <mva@mva.name> wrote:
> Sometimes I find myself in a situation, when I need to use both
> RESTRICT=fetch for the main distfile and allow fetch for additional
> ones (langpacks, extensions and so on).
> Sometimes it is even impossible to split that additions into separate
> package, since they might want to replace some file (for example, Dear
> Esther's translations).
>
> So, in that case, I think, it'd be useful to change SRC_URI
> behaviour a bit:
>
> for example:
>
> SRC_URI="
> restrict://dearesther-linux-06082013-bin #fetch restrict
> linguas_ru?
> ( http://www.dear-esther.com/translations/DE_Russian.rar )
> linguas_hu?
> ( http://www.dear-esther.com/translations/DE_Hungarian.rar )
> linguas_hu2?
> ( http://www.dear-esther.com/translations/DE_Hungarian2.rar ) "
> Alternatively it can be even:
>
> SRC_URI="
> restrict+http://foo.bar/moo-123.run # mirror-restrict or
> specifying a link for fetch-restrict (like for oracle-jdk)
Syntax-wise, one of the proposals for dealing with the explosion of
*DEPEND variables is a single variable plus labels. The same syntax
could be used here, so you'd do:
SRC_URI="http://blah/blah restrict: http://blah/other"
and so on, with the usual parentheses for restricting scope of labels.
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2013-06-15 16:35 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-15 8:56 [gentoo-dev] [RFC] SRC_URI behaviour Vadim A. Misbakh-Soloviov
2013-06-15 11:50 ` Diego Elio Pettenò
2013-06-15 12:12 ` Rich Freeman
2013-06-15 12:14 ` Diego Elio Pettenò
2013-06-15 13:06 ` Rich Freeman
2013-06-15 13:15 ` Diego Elio Pettenò
2013-06-15 13:26 ` Andreas K. Huettel
2013-06-15 21:15 ` Michael Weber
2013-06-15 21:17 ` Diego Elio Pettenò
2013-06-15 21:19 ` Diego Elio Pettenò
2013-06-15 21:21 ` Michael Weber
2013-06-15 21:24 ` Markos Chandras
2013-06-15 21:40 ` Michael Weber
2013-06-15 21:25 ` Diego Elio Pettenò
2013-06-15 22:38 ` Rick "Zero_Chaos" Farina
2013-06-15 13:34 ` Ulrich Mueller
2013-06-15 13:37 ` Diego Elio Pettenò
2013-06-15 13:47 ` Ulrich Mueller
2013-06-15 13:57 ` [gentoo-dev] " Michael Palimaka
2013-06-15 13:59 ` [gentoo-dev] " Diego Elio Pettenò
2013-06-15 12:34 ` Vadim A. Misbakh-Soloviov
2013-06-15 13:50 ` Luca Barbato
2013-06-15 12:48 ` Alexander V Vershilov
2013-06-15 12:58 ` Diego Elio Pettenò
2013-06-15 14:22 ` Pacho Ramos
2013-06-15 13:05 ` Michał Górny
2013-06-15 13:11 ` Vadim A. Misbakh-Soloviov
2013-06-15 13:16 ` Diego Elio Pettenò
2013-06-15 15:24 ` Brian Dolbec
2013-06-15 15:33 ` Rich Freeman
2013-06-15 15:43 ` Luca Barbato
2013-06-15 15:51 ` Rich Freeman
2013-06-15 16:37 ` Ciaran McCreesh
2013-06-16 7:52 ` Arfrever Frehtes Taifersar Arahesis
2013-06-15 20:16 ` Anthony G. Basile
2013-06-16 0:24 ` Zac Medico
2013-06-16 11:46 ` Luca Barbato
2013-06-16 12:12 ` Georg Rudoy
2013-06-16 12:18 ` Vadim A. Misbakh-Soloviov
2013-06-16 13:41 ` [gentoo-dev] " Michael Palimaka
2013-06-16 14:39 ` [gentoo-dev] " Rick "Zero_Chaos" Farina
2013-06-15 15:12 ` Rick "Zero_Chaos" Farina
2013-06-15 21:31 ` Michael Weber
2013-06-15 16:35 ` Ciaran McCreesh [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=20130615173502.0fc279a9@googlemail.com \
--to=ciaran.mccreesh@googlemail.com \
--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