| 1 |
> I was wanting to create an ebuild of Judy libraries: |
| 2 |
glad to hear it :) |
| 3 |
|
| 4 |
> http://sourceforge.net/projects/judy |
| 5 |
be sure to use the mirror://sourceforge syntax in the SRC_URI variable |
| 6 |
|
| 7 |
> You will notice that there is no version number in the software (because |
| 8 |
> the "big deal" about this software is the LGPLing of it). How can one |
| 9 |
> work around that? I have, so far, had to have an ebuild filename that |
| 10 |
> doesn't reflect the name of the tarball AND have had to explicitly state |
| 11 |
> the name of the tarball (and so not use ${P}). Can this be worked |
| 12 |
> around or should I contact the author of the software? |
| 13 |
in the SRC_URI, just explicitly type the filename rather than doing ${P}.tgz |
| 14 |
as for the ebuild naming, for now put the date stamp on it ... |
| 15 |
judy-20020627.ebuild |
| 16 |
|
| 17 |
> The other thing was the filename of the tarball starts with a capital |
| 18 |
> ("J"). Is this ok? It works (to have an ebuild file with a lowercase |
| 19 |
> first letter) but I am assuming if the tarball and the ebuild are to |
| 20 |
> have the same name, then this also needs to be fixed. |
| 21 |
source tarballs can be named however they want. |
| 22 |
you however better not even think about naming your ebuild with |
| 23 |
capital letters ;) |
| 24 |
capitalization is a big NONO with ebuild naming ... unforunately, |
| 25 |
not everyone has stuck to this. that does not mean you should also |
| 26 |
be one of these deviants :) |
| 27 |
|
| 28 |
hope this helps |
| 29 |
-mike |
Archives