| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On 06/15/2013 08:24 PM, Zac Medico wrote: |
| 5 |
> On 06/15/2013 06:05 AM, Michał Górny wrote: |
| 6 |
>> Dnia 2013-06-15, o godz. 15:56:53 |
| 7 |
>> "Vadim A. Misbakh-Soloviov" <mva@×××.name> napisał(a): |
| 8 |
>> |
| 9 |
>>> And, moreover, I guess, SRC_URI can even be used for VCS: |
| 10 |
>>> |
| 11 |
>>> SRC_URI=" |
| 12 |
>>> git+ssh://github.com/lol/moo.git |
| 13 |
>>> hg+ssh://bitbucket.org/lol/moo |
| 14 |
>>> svn+ssh://assembla.com/lol/moo |
| 15 |
>>> " |
| 16 |
>> |
| 17 |
>> It simply can't work. Don't even try to implement, it's waste of time. |
| 18 |
>> Just grep the tree, see how various packages use VCS-es. There's too |
| 19 |
>> many differences, too many needs and -- most importantly -- VCS-es |
| 20 |
>> change over time much more quickly than, say, unpackers. |
| 21 |
>> |
| 22 |
>> Even *if* we get a SRC_URI VCS support that works for all consumers, |
| 23 |
>> and that'd be awfully hard to do properly, it will eventually stop |
| 24 |
>> being 'good enough' and require further changes. It will just become |
| 25 |
>> never-ending story for a minor benefit. |
| 26 |
> |
| 27 |
> How about it we add a src_fetch phase, so that the VCS intricacies can |
| 28 |
> be delegated to ebuilds/eclasses (like they are now, but without having |
| 29 |
> to abuse src_unpack). If we include a way for src_fetch to communicate |
| 30 |
> changes in VCS revisions to the package manager, then we'll be able to |
| 31 |
> integrate functionality like smart-live-rebuild directly into the |
| 32 |
> package manager (as discussed in bug 182028 [1]). |
| 33 |
> |
| 34 |
> [1] http://bugs.gentoo.org/show_bug.cgi?id=182028 |
| 35 |
|
| 36 |
+1 on src_fetch in or out of the context of this thread. |
| 37 |
|
| 38 |
+1 on more granular fetch/mirror restrictions |
| 39 |
|
| 40 |
+-0 on VCS in SRC_URI, as I already stated I'm fine with the current |
| 41 |
functionality (aside from a vast desire for src_fetch phase). |
| 42 |
|
| 43 |
- -Zero |
| 44 |
-----BEGIN PGP SIGNATURE----- |
| 45 |
Version: GnuPG v2.0.19 (GNU/Linux) |
| 46 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
| 47 |
|
| 48 |
iQIcBAEBAgAGBQJRvc4cAAoJEKXdFCfdEflK990P/267Ej2p26SvRGItzFHtHakH |
| 49 |
EwDEQcLxfykfqs1p1AWjR2O9e7ZvW7PaF9EyFdypY0MxAu0faB24ek4OKGD4842L |
| 50 |
VbkQFXRjSOu1e+bLvQERofiVJ2/qSJZmg/phBsLwQiT0GVTm6ZXykZHSjfyTSALG |
| 51 |
6ip+bhwUnYGGmxs8oudb7abBy7HfqhFlA6GTnyonqeRXre4QxfWFi1Yup/mRFuWp |
| 52 |
XFwEoBe9t/95DBiXfjbvO5b6rlVEsChXuxELDUgP1dTdXTYKVRohs0lU6uZqlJkz |
| 53 |
RY+8p8bJDsZas0Ucw7+7ePb93mH+XCKz5bvMrz2YhEM//NTOC6QY9+F6iy/NevTp |
| 54 |
FNJeBCYUNKPpGzy4bm1649vDCqG51WK9iG8qtYO5G0y2QpkGZugUfALwalXK7L3M |
| 55 |
eThjhlGrn0LZvGXxkYNtHgimFg3VWDJXJLHipMkP5dUqC5t4HEaEqgdGTCpzwuka |
| 56 |
IUAahKdFLd3EZBlc3MHkYwuzfa0/MayOFiMcHKVV2+ONa5FcwkO8Rg6QJk5Xb7A1 |
| 57 |
NpPU87VampYERtaNcJKVACl8wR8Pltg4Y5xyz5Dgs+ga/gLvun6VePPO3WvKrAsS |
| 58 |
UirS6VqysSEFaZTFotW0LAN6N8+Mll90gjRRgJxaQcGy1IiZ7VXYGzb8Q9nRWL9n |
| 59 |
1PD6mk8hNr9C3aV14QzM |
| 60 |
=7DTn |
| 61 |
-----END PGP SIGNATURE----- |
Archives