[gentoo-dev] ebuild question, unpacking multi-packed tarballs

[gentoo-dev] ebuild question, unpacking multi-packed tarballs

[Michael Boman]

[-- Attachment #1: Type: text/plain, Size: 1009 bytes --]

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:

- The distribution tarball contains the GPG signature + source tarball,
  so I need to unpack it several times..

- Even thought it is using the same tarball there is 3 ways to get it
  compiled: server, client and stand-alone mode

First I am planning to have something like:

app-admin/samhain-server
app-admin/samhain-client
app-admin/samhain-standalone

Now, these ebuild names doesn't match the (first) tarball name:
"samhain_signed-1.7.2.tar.gz". In that tarball I have a new tarball called
"samhain-1.7.2.tar.gz"

How do I get about to unpack this multi-packed archive in a nice and
version independent way, so when next version comes out I just need to
bump up the version number of the ebuild?

Best regards
 Michael Boman

-- 
Michael Boman
Security Architect, SecureCiRT Pte Ltd
http://www.securecirt.com

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

Re: [gentoo-dev] ebuild question, unpacking multi-packed tarballs

[Benjamin Podszun]

[-- Attachment #1: Type: text/plain, Size: 1509 bytes --]

I'm not very experienced with ebuilds, but I'd start like this:


# Would make $MY_P equal to samhain-version
MY_P=samhain${P#samhain_server}
# Set the source-dir to the right directory-structure (only an example)
S=${WORKDIR}/${MY_P}/${MY_P}_src
# Where can we get the file and what's its name anyway?
SRC_URI="http://path/to/samhain/${MY_P}_signed.tar.gz

If there's anything wrong with the lines above, please correct me.
Better approaches would be nice as well..

Ben


On Wed, 2003-02-19 at 17:09, Michael Boman wrote:
> 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:
> 
> - The distribution tarball contains the GPG signature + source tarball,
>   so I need to unpack it several times..
> 
> - Even thought it is using the same tarball there is 3 ways to get it
>   compiled: server, client and stand-alone mode
> 
> First I am planning to have something like:
> 
> app-admin/samhain-server
> app-admin/samhain-client
> app-admin/samhain-standalone
> 
> Now, these ebuild names doesn't match the (first) tarball name:
> "samhain_signed-1.7.2.tar.gz". In that tarball I have a new tarball called
> "samhain-1.7.2.tar.gz"
> 
> How do I get about to unpack this multi-packed archive in a nice and
> version independent way, so when next version comes out I just need to
> bump up the version number of the ebuild?
> 
> Best regards
>  Michael Boman

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] ebuild question, unpacking multi-packed tarballs

[Thomas Arnhold]

[-- Attachment #1: Type: text/plain, Size: 1785 bytes --]

On Wed, Feb 19, 2003 at 05:44:04PM +0100, Benjamin Podszun wrote:
> I'm not very experienced with ebuilds, but I'd start like this:
> 
> # Would make $MY_P equal to samhain-version
> MY_P=samhain${P#samhain_server}
> # Set the source-dir to the right directory-structure (only an example)
> S=${WORKDIR}/${MY_P}/${MY_P}_src

I think S=${WORKDIR/${MY_P} would be ok.

> # Where can we get the file and what's its name anyway?
> SRC_URI="http://path/to/samhain/${MY_P}_signed.tar.gz
> 
> If there's anything wrong with the lines above, please correct me.
> Better approaches would be nice as well..
> 
> Ben
> 
> 
> On Wed, 2003-02-19 at 17:09, Michael Boman wrote:
> > 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:
> > 
> > - The distribution tarball contains the GPG signature + source tarball,
> >   so I need to unpack it several times..
> > 
> > - Even thought it is using the same tarball there is 3 ways to get it
> >   compiled: server, client and stand-alone mode
> > 
> > First I am planning to have something like:
> > 
> > app-admin/samhain-server
> > app-admin/samhain-client
> > app-admin/samhain-standalone
> > 
> > Now, these ebuild names doesn't match the (first) tarball name:
> > "samhain_signed-1.7.2.tar.gz". In that tarball I have a new tarball called
> > "samhain-1.7.2.tar.gz"
> > 
> > How do I get about to unpack this multi-packed archive in a nice and
> > version independent way, so when next version comes out I just need to
> > bump up the version number of the ebuild?
> > 
> > Best regards
> >  Michael Boman



-- 
www: http://slysoft.de
mail:  mail@slysoft.de
pgp-id:     0xD92FA6E7


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]