| 1 |
Hi, |
| 2 |
|
| 3 |
Zac Medico <zmedico@g.o>: |
| 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 |
| 22 |
> name. |
| 23 |
|
| 24 |
One needs exceptions for all kind of systems, for example I had to |
| 25 |
workaround Trac which adds ?format=raw to a tarball URI. There seems |
| 26 |
to be a solution in Trac as the guys from fedarahosted fixed the two I |
| 27 |
needed (tmpwatch, mlocate). So the -> operator is quite useful and I |
| 28 |
agree with David that the functionality is doubled. |
| 29 |
|
| 30 |
V-Li |
| 31 |
|
| 32 |
-- |
| 33 |
Christian Faulhammer, Gentoo Lisp project |
| 34 |
<URL:http://www.gentoo.org/proj/en/lisp/>, #gentoo-lisp on FreeNode |
| 35 |
|
| 36 |
<URL:http://www.faulhammer.org/> |
Archives