| 1 |
Mike Frysinger <vapier@g.o> writes: |
| 2 |
|
| 3 |
> > You will notice that there is no version number in the software (because |
| 4 |
> > the "big deal" about this software is the LGPLing of it). How can one |
| 5 |
> > work around that? I have, so far, had to have an ebuild filename that |
| 6 |
> > doesn't reflect the name of the tarball AND have had to explicitly state |
| 7 |
> > the name of the tarball (and so not use ${P}). Can this be worked |
| 8 |
> > around or should I contact the author of the software? |
| 9 |
> in the SRC_URI, just explicitly type the filename rather than doing ${P}.tgz |
| 10 |
> as for the ebuild naming, for now put the date stamp on it ... |
| 11 |
> judy-20020627.ebuild |
| 12 |
|
| 13 |
I don't believe this is enough. Since the filename does not contain |
| 14 |
unique versioning information, it is susceptible to the problem where |
| 15 |
the digest becomes out of date with package in SRC_URI. |
| 16 |
|
| 17 |
You need to make a note of this when you submit the ebuild to |
| 18 |
bugs.gentoo.org. The developer who handles it will probably download |
| 19 |
the source package rename it to include some version information |
| 20 |
(probably just a date), create the digest for the ebuild and then |
| 21 |
upload the renamed source package it to the distfiles sub-dir on the |
| 22 |
mirrors. |
| 23 |
|
| 24 |
I think... |
| 25 |
|
| 26 |
Matt |
| 27 |
-- |
| 28 |
Matthew Kennedy |
| 29 |
Gentoo Linux Developer |
| 30 |
Bugs go to http://bugs.gentoo.org! |
| 31 |
|
| 32 |
Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x6C25B0A2 |
| 33 |
Finger Print: 0C61 0CBC C669 5F26 8DBF 006D FBAB 30EA 6C25 B0A2 |
Archives