Re: [gentoo-dev] [RFC] SRC_URI behaviour

["Rick \"Zero_Chaos\" Farina" <zerochaos@gentoo.org>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 06/15/2013 04:56 AM, Vadim A. Misbakh-Soloviov 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)
> "

I think something like this would be extremely valuable.  Sometimes one
file is fetch restricted and the rest are not and we currently don't
handle that at all.  If you want to write an implementation for it, I
think it's great.
> 
> And, moreover, I guess, SRC_URI can even be used for VCS:
> 
> SRC_URI="
> 	git+ssh://github.com/lol/moo.git
> 	hg+ssh://bitbucket.org/lol/moo
> 	svn+ssh://assembla.com/lol/moo
> "
> 
> And it can also be extendable:
> 
> SRC_URI="
> 	hg+http://prosody.im/trunk
> 	modules? ( hg+https://prosody-modules.googlecode.com/hg )
> "

I don't quite agree with "Over my dead CVS access" but yeah, this isn't
really a great idea or needed.  The current way to fetch live things is
both functional and simple enough to be in very wide use.  There is
currently no need for improvement in my eyes, and I'm not sure this
could be considered improvement anyway.

Thanks,
Zero

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJRvIR6AAoJEKXdFCfdEflKns8QAJq4N0VDwoLTda5ptmEXhrH9
O6CBNAvz+f4cG/lA9bKRxqjWfce44KQbSCO/nieabLLNTNEtNn+xbdz5AHGJxEKa
muxJNhHiUNjqN6J9IyXNqlpV1hC0mrxroN9hTL7HnryJKzLXx7t+IIpnjyFZDdho
bw9PH1boAt7YN4FRctoV3ALAXU3zY+v/rJNAoDAwfajteZRipRPEnfGEVeuKjm7o
8PY39eBGmgKzQLoz67RTVVgNwOnsyHeJWJX8XWXaURK/2Lh/jBOdSP23xgh50K20
e4zDdRYHP6YH0vFraIjo9d17NtuuzI3SW78BL8JMHdNbQl7XY5khN/Z/KuKy3ydH
ccQba25Snkuz0tL+DBnpMb5JkLz02Jup2ug6VqTPwCTtCykRvDF9jf0JLEcNfEd2
8Tkqn4Jah5+zqYox0xIxlJmwLvnlH8Jc7OLuZEIEjt4x3tEXf8mDSSpWV90aI+A2
7dHi9ealEPAPTdt7LqHuJ6ic7akPH4o/lTE+Yp/OcSIUrAfWThxiLUkgD3vbBh/E
ZzQFuIqrtptXWP8jGhw01bcqRp6MfOSuCe5G6pEdR0N8Ud5qnyZyPWeMf/1hUxMy
g4RMge28KDscnQy+Z0D0BNGSyYuru5mP+vLnfqKHnUjNzxSSbIXj3F98nXykhVvQ
SyGs/KBmBdtLVGqrqVWl
=gBw2
-----END PGP SIGNATURE-----