| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
David Leverton wrote: |
| 5 |
> 2008/9/4 Zac Medico <zmedico@g.o>: |
| 6 |
>> * The 'unpack' helper function recognizes ;sf=tbz2 and ;sf=tgz |
| 7 |
>> extensions, for interoperability with gitweb. |
| 8 |
>> |
| 9 |
>> * SRC_URI supports a syntax extension which allows customization |
| 10 |
>> of output file names by using a "->" operator. |
| 11 |
> |
| 12 |
> Is it useful to have both of these? The former seems awfully |
| 13 |
> specialised for a general format like ebuilds, and can be replaced |
| 14 |
> with |
| 15 |
> |
| 16 |
> COMMIT="1234..." |
| 17 |
> SRC_URI="http://git.example.org/?p=foo.git;a=snapshot;h=${COMMIT};sf=tbz2 |
| 18 |
> -> foo-${COMMIT}.tar.bz2" |
| 19 |
|
| 20 |
Both approaches are essentially equivalent but it's a little simpler |
| 21 |
for ebuild writer if they don't have to customize the output file name. |
| 22 |
|
| 23 |
- -- |
| 24 |
Thanks, |
| 25 |
Zac |
| 26 |
-----BEGIN PGP SIGNATURE----- |
| 27 |
Version: GnuPG v2.0.9 (GNU/Linux) |
| 28 |
|
| 29 |
iEYEARECAAYFAkjA3WUACgkQ/ejvha5XGaOpJgCbBUuFc2POX2nE9An065fC+b2z |
| 30 |
zTsAoIXp+CyP6Dy15OlcdYjNktoo7/Hq |
| 31 |
=xJss |
| 32 |
-----END PGP SIGNATURE----- |
Archives