1 |
Alec Warner wrote: |
2 |
|
3 |
> On Sat, Sep 6, 2008 at 4:43 AM, Steve Long <slong@××××××××××××××××××.uk> |
4 |
> wrote: |
5 |
>> Christian Faulhammer wrote: |
6 |
>> |
7 |
>>> Zac Medico <zmedico@g.o>: |
8 |
>>>> Both approaches are essentially equivalent but it's a little simpler |
9 |
>>>> for ebuild writer if they don't have to customize the output file |
10 |
>>>> name. |
11 |
>>> |
12 |
>>> One needs exceptions for all kind of systems, for example I had to |
13 |
>>> workaround Trac which adds ?format=raw to a tarball URI. There seems |
14 |
>>> to be a solution in Trac as the guys from fedarahosted fixed the two I |
15 |
>>> needed (tmpwatch, mlocate). So the -> operator is quite useful and I |
16 |
>>> agree with David that the functionality is doubled. |
17 |
>>> |
18 |
>> Clearly src-uri transformation is useful. Others have given examples of |
19 |
>> how it would be useful to an eclass. Irrespective of how the actual |
20 |
>> transform is done in the ;sf=tbz2 case, both _are_ valid use-cases. |
21 |
>> |
22 |
>> As such I don't see any reason not to put it in the EAPI. Future |
23 |
>> extensions can be trialled in eutils, and these can both be allowed |
24 |
>> syntax for other package managers to comply with (one implementation has |
25 |
>> already been given) and ebuild devs to feel comfortable using in the |
26 |
>> Gentoo tree. Why slow the innovation down? It's good enough for use |
27 |
>> as-is. |
28 |
> |
29 |
> Because then we have to wait for all the PM's to implement this |
30 |
> magical code; where if we put it in eutils |
31 |
> we can use it right now (and most overlays can use it too). 'Why slow |
32 |
> the innovation down?' :) |
33 |
> |
34 |
Eh? I thought it was for the portage team to define the EAPI for Gentoo, |
35 |
published so that others can interoperate? And how are other Package |
36 |
Managers going to feel if they have to keep checking eutils for what it |
37 |
does to stay current with the tree, as opposed to looking in the EAPI doc? |
38 |
|
39 |
This is wandering into -project territory however, imo, since there's no |
40 |
_technical_ reason not to allow the proposed usage in the EAPI. All I've |
41 |
heard so far is "we might want to extend it later." |