| 1 |
I'm not very experienced with ebuilds, but I'd start like this: |
| 2 |
|
| 3 |
|
| 4 |
# Would make $MY_P equal to samhain-version |
| 5 |
MY_P=samhain${P#samhain_server} |
| 6 |
# Set the source-dir to the right directory-structure (only an example) |
| 7 |
S=${WORKDIR}/${MY_P}/${MY_P}_src |
| 8 |
# Where can we get the file and what's its name anyway? |
| 9 |
SRC_URI="http://path/to/samhain/${MY_P}_signed.tar.gz |
| 10 |
|
| 11 |
If there's anything wrong with the lines above, please correct me. |
| 12 |
Better approaches would be nice as well.. |
| 13 |
|
| 14 |
Ben |
| 15 |
|
| 16 |
|
| 17 |
On Wed, 2003-02-19 at 17:09, Michael Boman wrote: |
| 18 |
> I am trying to create ebuilds for samhain (http://la-samhna.de/samhain/index.html), both client/server and stand-alone mode. I have some problems with it thought: |
| 19 |
> |
| 20 |
> - The distribution tarball contains the GPG signature + source tarball, |
| 21 |
> so I need to unpack it several times.. |
| 22 |
> |
| 23 |
> - Even thought it is using the same tarball there is 3 ways to get it |
| 24 |
> compiled: server, client and stand-alone mode |
| 25 |
> |
| 26 |
> First I am planning to have something like: |
| 27 |
> |
| 28 |
> app-admin/samhain-server |
| 29 |
> app-admin/samhain-client |
| 30 |
> app-admin/samhain-standalone |
| 31 |
> |
| 32 |
> Now, these ebuild names doesn't match the (first) tarball name: |
| 33 |
> "samhain_signed-1.7.2.tar.gz". In that tarball I have a new tarball called |
| 34 |
> "samhain-1.7.2.tar.gz" |
| 35 |
> |
| 36 |
> How do I get about to unpack this multi-packed archive in a nice and |
| 37 |
> version independent way, so when next version comes out I just need to |
| 38 |
> bump up the version number of the ebuild? |
| 39 |
> |
| 40 |
> Best regards |
| 41 |
> Michael Boman |
Archives