Gentoo Archives: gentoo-dev

From: "Rick \\\"Zero_Chaos\\\" Farina" <zerochaos@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] [RFC] SRC_URI behaviour
Date: Sat, 15 Jun 2013 15:12:05
Message-Id: 51BC847A.6050109@gentoo.org
In Reply to: [gentoo-dev] [RFC] SRC_URI behaviour by "Vadim A. Misbakh-Soloviov"
1 -----BEGIN PGP SIGNED MESSAGE-----
2 Hash: SHA1
3
4 On 06/15/2013 04:56 AM, Vadim A. Misbakh-Soloviov wrote:
5 > Sometimes I find myself in a situation, when I need to use both
6 > RESTRICT=fetch for the main distfile and allow fetch for additional ones
7 > (langpacks, extensions and so on).
8 > Sometimes it is even impossible to split that additions into separate
9 > package, since they might want to replace some file (for example, Dear
10 > Esther's translations).
11 >
12 > So, in that case, I think, it'd be useful to change SRC_URI behaviour a
13 > bit:
14 >
15 > for example:
16 >
17 > SRC_URI="
18 > restrict://dearesther-linux-06082013-bin #fetch restrict
19 > linguas_ru? ( http://www.dear-esther.com/translations/DE_Russian.rar )
20 > linguas_hu? ( http://www.dear-esther.com/translations/DE_Hungarian.rar )
21 > linguas_hu2? (
22 > http://www.dear-esther.com/translations/DE_Hungarian2.rar )
23 > "
24 > Alternatively it can be even:
25 >
26 > SRC_URI="
27 > restrict+http://foo.bar/moo-123.run # mirror-restrict or specifying a
28 > link for fetch-restrict (like for oracle-jdk)
29 > "
30
31 I think something like this would be extremely valuable. Sometimes one
32 file is fetch restricted and the rest are not and we currently don't
33 handle that at all. If you want to write an implementation for it, I
34 think it's great.
35 >
36 > And, moreover, I guess, SRC_URI can even be used for VCS:
37 >
38 > SRC_URI="
39 > git+ssh://github.com/lol/moo.git
40 > hg+ssh://bitbucket.org/lol/moo
41 > svn+ssh://assembla.com/lol/moo
42 > "
43 >
44 > And it can also be extendable:
45 >
46 > SRC_URI="
47 > hg+http://prosody.im/trunk
48 > modules? ( hg+https://prosody-modules.googlecode.com/hg )
49 > "
50
51 I don't quite agree with "Over my dead CVS access" but yeah, this isn't
52 really a great idea or needed. The current way to fetch live things is
53 both functional and simple enough to be in very wide use. There is
54 currently no need for improvement in my eyes, and I'm not sure this
55 could be considered improvement anyway.
56
57 Thanks,
58 Zero
59
60 -----BEGIN PGP SIGNATURE-----
61 Version: GnuPG v2.0.19 (GNU/Linux)
62 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
63
64 iQIcBAEBAgAGBQJRvIR6AAoJEKXdFCfdEflKns8QAJq4N0VDwoLTda5ptmEXhrH9
65 O6CBNAvz+f4cG/lA9bKRxqjWfce44KQbSCO/nieabLLNTNEtNn+xbdz5AHGJxEKa
66 muxJNhHiUNjqN6J9IyXNqlpV1hC0mrxroN9hTL7HnryJKzLXx7t+IIpnjyFZDdho
67 bw9PH1boAt7YN4FRctoV3ALAXU3zY+v/rJNAoDAwfajteZRipRPEnfGEVeuKjm7o
68 8PY39eBGmgKzQLoz67RTVVgNwOnsyHeJWJX8XWXaURK/2Lh/jBOdSP23xgh50K20
69 e4zDdRYHP6YH0vFraIjo9d17NtuuzI3SW78BL8JMHdNbQl7XY5khN/Z/KuKy3ydH
70 ccQba25Snkuz0tL+DBnpMb5JkLz02Jup2ug6VqTPwCTtCykRvDF9jf0JLEcNfEd2
71 8Tkqn4Jah5+zqYox0xIxlJmwLvnlH8Jc7OLuZEIEjt4x3tEXf8mDSSpWV90aI+A2
72 7dHi9ealEPAPTdt7LqHuJ6ic7akPH4o/lTE+Yp/OcSIUrAfWThxiLUkgD3vbBh/E
73 ZzQFuIqrtptXWP8jGhw01bcqRp6MfOSuCe5G6pEdR0N8Ud5qnyZyPWeMf/1hUxMy
74 g4RMge28KDscnQy+Z0D0BNGSyYuru5mP+vLnfqKHnUjNzxSSbIXj3F98nXykhVvQ
75 SyGs/KBmBdtLVGqrqVWl
76 =gBw2
77 -----END PGP SIGNATURE-----

Replies

Subject Author
Re: [gentoo-dev] [RFC] SRC_URI behaviour Michael Weber <xmw@g.o>