[gentoo-user] convert rpm to ebuild

[gentoo-user] convert rpm to ebuild

[Florian Philipp]

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

Hi!

I thought this question would be quiet common but I've been unable to get an 
answer googling and looking through howtos. Actually there are some links in 
an old thread on forums.gentoo.org but its target seems to have moved.

Anyway, how do I install packages in .rpm or .deb without messing up portage? 
Is there something like "alien"?

Thanks in advance
Florian Philipp 

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

Re: [gentoo-user] convert rpm to ebuild

[darren kirby]

quoth the Florian Philipp:
> Hi!
>
> I thought this question would be quiet common but I've been unable to get
> an answer googling and looking through howtos. Actually there are some
> links in an old thread on forums.gentoo.org but its target seems to have
> moved.
>
> Anyway, how do I install packages in .rpm or .deb without messing up
> portage? Is there something like "alien"?
>
> Thanks in advance
> Florian Philipp

Well, you can install RPM...

# emerge -p rpm

You could then, presumably, install the RPM, though I have not ever tried 
this:
# rpm -i foopackage.i386.rpm

Use AYOR (at your own risk...), as I have no idea what repercussions this may 
have. Does RPM have a --pretend option?

I have used `ebuild`s 'rpm' target to make RPMs of software with ebuilds which 
is essentially the opposite of what you want. Works good.

-d
-- 
darren kirby :: Part of the problem since 1976 :: http://badcomputer.org
"...the number of UNIX installations has grown to 10, with more expected..."
- Dennis Ritchie and Ken Thompson, June 1972
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] convert rpm to ebuild

[Bo Ørsted Andresen]

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

On Thursday 10 May 2007 21:06:13 Florian Philipp wrote:
> I thought this question would be quiet common but I've been unable to get
> an answer googling and looking through howtos. Actually there are some
> links in an old thread on forums.gentoo.org but its target seems to have
> moved.

Well, you can always make an ebuild for it.

http://devmanual.gentoo.org/ebuild-writing/functions/src_unpack/rpm-sources/index.html

-- 
Bo Andresen

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

Re: [gentoo-user] convert rpm to ebuild

[Florian Philipp]

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

Am Donnerstag 10 Mai 2007 21:53 schrieb Bo Ørsted Andresen:
> On Thursday 10 May 2007 21:06:13 Florian Philipp wrote:
> > I thought this question would be quiet common but I've been unable to get
> > an answer googling and looking through howtos. Actually there are some
> > links in an old thread on forums.gentoo.org but its target seems to have
> > moved.
>
> Well, you can always make an ebuild for it.
>
> http://devmanual.gentoo.org/ebuild-writing/functions/src_unpack/rpm-sources
>/index.html

Argh, that's the broken link I was talking about, thanks!

However, it seems as if there is no "easy" way to perform it and there are 
still some questions for me:

1. This page provides no way to handle a binary-only rpm, just sources. Yet, 
sources are no problem since they should be available as a tarball or in 
portage itself while rpms of proprietary closed-source software are quiet 
common. I could transfer them into a .deb-archive using "alien" which leads 
me to problem number 2 ...

2. This page [1] tells me how to extract a .deb-package and that I "could just 
extract [its binaries] to /" But this doesn't help me because portage does 
not know about this package, its dependencies and so on. I could break my 
system quiet easily this way.

[1] 
http://devmanual.gentoo.org/ebuild-writing/functions/src_unpack/deb-sources/index.html

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

Re: [gentoo-user] convert rpm to ebuild

[darren kirby]

quoth the b.n.:
> darren kirby ha scritto:
> > Well, you can install RPM...
> >
> > # emerge -p rpm
> >
> > You could then, presumably, install the RPM, though I have not ever tried
> > this:
> > # rpm -i foopackage.i386.rpm
>
> I fear this way Portage would not be aware of the package being
> installed. Am I wrong?
>
> m.

I've no idea, but likely not. To tell the truth I was hoping the OP would be 
brave and find out ;)

I was thinking he just had a one-off app he needed installed, and combined 
with some 'package.provided' alchemy he may be able to get the result he 
needed, however, in his response it seems this is not the case so...

-d
-- 
darren kirby :: Part of the problem since 1976 :: http://badcomputer.org
"...the number of UNIX installations has grown to 10, with more expected..."
- Dennis Ritchie and Ken Thompson, June 1972
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] convert rpm to ebuild

[Bo Ørsted Andresen]

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

On Thursday 10 May 2007 22:16:59 Florian Philipp wrote:
> > > I thought this question would be quiet common but I've been unable to
> > > get an answer googling and looking through howtos. Actually there are
> > > some links in an old thread on forums.gentoo.org but its target seems
> > > to have moved.
> >
> > Well, you can always make an ebuild for it.
> >
> > http://devmanual.gentoo.org/ebuild-writing/functions/src_unpack/rpm-sources/index.html
>
> Argh, that's the broken link I was talking about, thanks!
>
> However, it seems as if there is no "easy" way to perform it and there are
> still some questions for me:
>
> 1. This page provides no way to handle a binary-only rpm, just sources.
> Yet, sources are no problem since they should be available as a tarball or
> in portage itself while rpms of proprietary closed-source software are
> quiet common. I could transfer them into a .deb-archive using "alien" which
> leads me to problem number 2 ...

There are plenty of ebuilds for binary only packages in the tree. The above
link helps you to unpack the binary files to $WORKDIR. After that you can use
the install functions [1] (or cp or whatever) in src_install() to install
to the image ($D). And perhaps you need and env.d file or whatever else may be
missing (for additions to *PATH variables).

When all of that is done you can emerge it. And no, a .deb isn't any better.

[1] http://devmanual.gentoo.org/function-reference/install-functions/index.html

-- 
Bo Andresen

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

Re: [gentoo-user] convert rpm to ebuild

[Bo Ørsted Andresen]

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

On Friday 11 May 2007 00:12:43 b.n. wrote:
> > # rpm -i foopackage.i386.rpm
>
> I fear this way Portage would not be aware of the package being
> installed. Am I wrong?

No, you are correct.

-- 
Bo Andresen

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

Re: [gentoo-user] convert rpm to ebuild

[Florian Philipp]

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

> quoth the b.n.:
> > darren kirby ha scritto:
> > > Well, you can install RPM...
> > >
> > > # emerge -p rpm
> > >
> > > You could then, presumably, install the RPM, though I have not ever
> > > tried this:
> > > # rpm -i foopackage.i386.rpm
> >
> > I fear this way Portage would not be aware of the package being
> > installed. Am I wrong?
> >
> > m.
>
> I've no idea, but likely not. To tell the truth I was hoping the OP would
> be brave and find out ;)
>
> I was thinking he just had a one-off app he needed installed, and combined
> with some 'package.provided' alchemy he may be able to get the result he
> needed, however, in his response it seems this is not the case so...
>
> -d
> --
> darren kirby 

Maybe I should formulate another question: Where is the big difference between 
a binary ebuild and a binary rpm / deb and why is it so hard to convert them? 

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

Re: [gentoo-user] convert rpm to ebuild

[Florian Philipp]

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

Am Donnerstag 10 Mai 2007 22:29 schrieb Bo Ørsted Andresen:
> On Thursday 10 May 2007 22:16:59 Florian Philipp wrote:
> > > > I thought this question would be quiet common but I've been unable to
> > > > get an answer googling and looking through howtos. Actually there are
> > > > some links in an old thread on forums.gentoo.org but its target seems
> > > > to have moved.
> > >
> > > Well, you can always make an ebuild for it.
> > >
> > > http://devmanual.gentoo.org/ebuild-writing/functions/src_unpack/rpm-sou
> > >rces/index.html
> >
> > Argh, that's the broken link I was talking about, thanks!
> >
> > However, it seems as if there is no "easy" way to perform it and there
> > are still some questions for me:
> >
> > 1. This page provides no way to handle a binary-only rpm, just sources.
> > Yet, sources are no problem since they should be available as a tarball
> > or in portage itself while rpms of proprietary closed-source software are
> > quiet common. I could transfer them into a .deb-archive using "alien"
> > which leads me to problem number 2 ...
>
> There are plenty of ebuilds for binary only packages in the tree. The above
> link helps you to unpack the binary files to $WORKDIR. After that you can
> use the install functions [1] (or cp or whatever) in src_install() to
> install to the image ($D). And perhaps you need and env.d file or whatever
> else may be missing (for additions to *PATH variables).
>
> When all of that is done you can emerge it. And no, a .deb isn't any
> better.
>
> [1]
> http://devmanual.gentoo.org/function-reference/install-functions/index.html

Hmm, looks quiet complicated. Maybe there is a simpler solution:

Since I can install an rpm after emerging rpm itself, there is no need to 
convert it. All I have to do is to make portage aware of this package. Of 
course I would have to take care of dependencies myself and let rpm forget 
about dependencies since it doesn't know about my emerged packages.

Could that work? How do I do it?

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

Re: [gentoo-user] convert rpm to ebuild

[Paul Varner]

On Thu, 2007-05-10 at 22:29 +0200, Bo Ørsted Andresen wrote:
> On Thursday 10 May 2007 22:16:59 Florian Philipp wrote:
> >
> > 1. This page provides no way to handle a binary-only rpm, just sources.
> > Yet, sources are no problem since they should be available as a tarball or
> > in portage itself while rpms of proprietary closed-source software are
> > quiet common. I could transfer them into a .deb-archive using "alien" which
> > leads me to problem number 2 ...
> 
> There are plenty of ebuilds for binary only packages in the tree. The above
> link helps you to unpack the binary files to $WORKDIR. After that you can use
> the install functions [1] (or cp or whatever) in src_install() to install
> to the image ($D). And perhaps you need and env.d file or whatever else may be
> missing (for additions to *PATH variables).
> 
> When all of that is done you can emerge it. And no, a .deb isn't any better.
> 
> [1] http://devmanual.gentoo.org/function-reference/install-functions/index.html
> 

One example from the tree is media-video/realplayer. It is a package
that installs a binary package from an rpm.

Regards,
Paul
--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] convert rpm to ebuild

[Neil Bothwick]

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

On Thu, 10 May 2007 22:36:41 +0200, Florian Philipp wrote:

> Maybe I should formulate another question: Where is the big difference
> between a binary ebuild and a binary rpm / deb and why is it so hard to
> convert them? 

The only real difference is the packaging method. The extra information
contained in RPM files isn't used by portage as it is replicated in the
ebuild. Where binary packages are provided in a choice of RPM or tarball
formats, such as VMware, the ebuilds usually use the tarball.


-- 
Neil Bothwick

Foolproof operation: No provision for adjustment.

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

Re: [gentoo-user] convert rpm to ebuild

[Jesús Guerrero]

El Thu, 10 May 2007 22:36:41 +0200
Florian Philipp <f.philipp@addcom.de> escribió:

> Maybe I should formulate another question: Where is the big
> difference between a binary ebuild and a binary rpm / deb and why is
> it so hard to convert them? 

The difference is that Gentoo is not RPM based. Could it supoprt RPM?
Yes, and also DEB files, and also..... As you see, each distro has it's
own packaging system.

Gentoo ebuilds are nothing more -ultimately- than bash scripts which
provides an easy way to build stuff from source (RPM is by no means
oriented on that direction, though there are also source RPM, but they
are not the normal thing, like binary ebuilds are not normal either).

Sure ebuilds can use data extracted from RPMs, that is no problem. But
for any ebuild, a given RPM is nothing more than a tarball containing
binaries, and not a proper package.

-- Jesús Guerrero
--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] convert rpm to ebuild

[b.n.]

darren kirby ha scritto:

> Well, you can install RPM...
> 
> # emerge -p rpm
> 
> You could then, presumably, install the RPM, though I have not ever tried 
> this:
> # rpm -i foopackage.i386.rpm

I fear this way Portage would not be aware of the package being 
installed. Am I wrong?

m.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] convert rpm to ebuild

[Bo Ørsted Andresen]

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

On Thursday 10 May 2007 22:36:41 Florian Philipp wrote:
> Maybe I should formulate another question: Where is the big difference
> between a binary ebuild and a binary rpm / deb and why is it so hard to
> convert them?

Gentoo is a source based distro. Usually in Gentoo binary packages are placed 
in /opt. Running revdep-rebuild to rebuild a binary package isn't going to do 
a thing. Sometimes paths need to be added to *PATH environment variables.

Sure the package managers could (at least paludis or pkgcore if anyone skilled 
enough would do the job) be made to support rpm's or debian packages but 
there would still be binary compatibility issues to tackle...

Also I don't really agree that creating an ebuild is so hard.

Hope that answers some of it..

-- 
Bo Andresen

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

Re: [gentoo-user] convert rpm to ebuild

[darren kirby]

quoth the Florian Philipp:
> Maybe I should formulate another question: Where is the big difference
> between a binary ebuild and a binary rpm / deb and why is it so hard to
> convert them?

Another thought:

Unless I've missed it, you've not mentioned *what* it is you have an RPM for. 
Have you checked bugzilla, and all the various overlays yet to see if there 
*is* a user-contributed ebuild for it?

-d
-- 
darren kirby :: Part of the problem since 1976 :: http://badcomputer.org
"...the number of UNIX installations has grown to 10, with more expected..."
- Dennis Ritchie and Ken Thompson, June 1972
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] convert rpm to ebuild

[Hans-Werner Hilse]

Hi,

On Thu, 10 May 2007 22:50:42 +0200
Florian Philipp <f.philipp@addcom.de> wrote:

> Since I can install an rpm after emerging rpm itself, there is no need to 
> convert it. All I have to do is to make portage aware of this package. Of 
> course I would have to take care of dependencies myself and let rpm forget 
> about dependencies since it doesn't know about my emerged packages.
> 
> Could that work?

If you're lucky and actually *do* manage to get the dependencies right.
I wouldn't bet a cent on it, at least, if we're talking about a dynamic
executable.

> How do I do it?

$ rpm -i --nodeps my.rpm

-hwh
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] convert rpm to ebuild

[Aleksandar L. Dimitrov]

On Thu, 10 May 2007 22:12:43 +0000
"b.n." <brullonulla@gmail.com> wrote:

> darren kirby ha scritto:
> 
> > Well, you can install RPM...
> > 
> > # emerge -p rpm
> > 
> > You could then, presumably, install the RPM, though I have not ever
> > tried this:
> > # rpm -i foopackage.i386.rpm
> 
> I fear this way Portage would not be aware of the package being 
> installed. Am I wrong?
> 
> m.

Hi,

no, I suppose you are perfectly right. But suppose there is a PREFIX for
the rpm-program and this could be set to something like /usr/local
or /usr/local/rpm. This way both trees would be independent - of course
you would also have to keep a second tree up-to-date.

Regards, Aleks
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] convert rpm to ebuild

[Randy Barlow]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Bo Ørsted Andresen wrote:
> On Friday 11 May 2007 00:12:43 b.n. wrote:
>>> # rpm -i foopackage.i386.rpm
>> I fear this way Portage would not be aware of the package being
>> installed. Am I wrong?
> 
> No, you are correct.

This is what package.provided is for...

R



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGQ+a97So1xaF/eR8RAnLIAJ9UUcEsHf/3nJwY0IAdx1fZv8ZUkQCeLe84
1oUXjOLsP9TnDpd++PUbs6Y=
=lZVt
-----END PGP SIGNATURE-----
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] convert rpm to ebuild

[Dirk Heinrichs]

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

Am Donnerstag, 10. Mai 2007 schrieb ext Florian Philipp:

> Anyway, how do I install packages in .rpm or .deb without messing up
> portage?

Write an ebuild for it. portage uses rpm packages just like tar.gz.

See http://bugs.gentoo.org/show_bug.cgi?id=103406 for an example ebuild that 
uses a src.rpm.

HTH...

	Dirk
-- 
Dirk Heinrichs          | Tel:  +49 (0)162 234 3408
Configuration Manager   | Fax:  +49 (0)211 47068 111
Capgemini Deutschland   | Mail: dirk.heinrichs@capgemini.com
Wanheimerstraße 68      | Web:  http://www.capgemini.com
D-40468 Düsseldorf      | ICQ#: 110037733
GPG Public Key C2E467BB | Keyserver: www.keyserver.net

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

Re: [gentoo-user] convert rpm to ebuild

[Florian Philipp]

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

> quoth the Florian Philipp:
> > Maybe I should formulate another question: Where is the big difference
> > between a binary ebuild and a binary rpm / deb and why is it so hard to
> > convert them?
>
> Another thought:
>
> Unless I've missed it, you've not mentioned *what* it is you have an RPM
> for. Have you checked bugzilla, and all the various overlays yet to see if
> there *is* a user-contributed ebuild for it?
>
> darren kirby

My problem is that I don't have any - yet. 

I'm going to work for a company that uses RedHat and I will have to use my 
private laptop (Gentoo, of course).
Since they develop software themselves I fear that I will have to use some of 
their customized or self-developed and not published software without access 
to the source (I don't think they'll trust me so much in the beginning).

Well, it doesn't seem like there is an easy solution so I will play around 
with rpms in a chroot-jail to get used to it. If everything goes wrong I can 
still switch to an rpm-based distribution ...

Thank you guys! You have given me alot of inspiration and hints. 

Florian Philipp

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

Re: [gentoo-user] convert rpm to ebuild

[Nistor Andrei]

On Thursday 10 May 2007, Florian Philipp wrote:
> Hi!
>
> I thought this question would be quiet common but I've been unable to get
> an answer googling and looking through howtos. Actually there are some
> links in an old thread on forums.gentoo.org but its target seems to have
> moved.
>
> Anyway, how do I install packages in .rpm or .deb without messing up
> portage? Is there something like "alien"?
>
> Thanks in advance
> Florian Philipp


Just a thought... I think you could use alien to convert the rpm to a tar.gz, 
then use "emerge /path/to/whatever.tar.gz". (IIRC that's a way you can 
install a binary package...). That should make portage aware of the package 
being installed, but I think that you must install the deps by hand...
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] convert rpm to ebuild

[Neil Bothwick]

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

On Fri, 11 May 2007 12:43:50 +0300, Nistor Andrei wrote:

> Just a thought... I think you could use alien to convert the rpm to a
> tar.gz,

Use rpm2tgxz to do that.

> then use "emerge /path/to/whatever.tar.gz". (IIRC that's a way
> you can install a binary package...). That should make portage aware of
> the package being installed, but I think that you must install the deps
> by hand...

That won't work, emerge can only work with ebuilds or portage binary
packages. You can either write your own ebuild to install the binary,
which is pretty straightforward, or simply unpack it to /.

As these are private, company packages, nothing else in the tree is going
to depend on it, so you don't really need to install it via portage,
although it does make tracking the package's dependencies easier.


-- 
Neil Bothwick

Make like a tree and leave.

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

Re: [gentoo-user] convert rpm to ebuild

[Nistor Andrei]

On Friday 11 May 2007, Neil Bothwick wrote:
> On Fri, 11 May 2007 12:43:50 +0300, Nistor Andrei wrote:
> > Just a thought... I think you could use alien to convert the rpm to a
> > tar.gz,
>
> Use rpm2tgxz to do that.
>
> > then use "emerge /path/to/whatever.tar.gz". (IIRC that's a way
> > you can install a binary package...). That should make portage aware of
> > the package being installed, but I think that you must install the deps
> > by hand...
>
> That won't work, emerge can only work with ebuilds or portage binary
> packages. You can either write your own ebuild to install the binary,
> which is pretty straightforward, or simply unpack it to /.
>
Portage binary packages aren't actually .tar.gz archives?
> As these are private, company packages, nothing else in the tree is going
> to depend on it, so you don't really need to install it via portage,
> although it does make tracking the package's dependencies easier.


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] convert rpm to ebuild

[Neil Bothwick]

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

On Fri, 11 May 2007 13:25:46 +0300, Nistor Andrei wrote:

> > That won't work, emerge can only work with ebuilds or portage binary
> > packages. You can either write your own ebuild to install the binary,
> > which is pretty straightforward, or simply unpack it to /.
> >  
> Portage binary packages aren't actually .tar.gz archives?

No, they are tar.bz2 archives with some metadata appended. without that
metadata, portage cannot create an entry in the package database.


-- 
Neil Bothwick

Life is pleasant. Death is peaceful. Its the transition thats
troublesome. - Isaac Asimov

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

RE: [gentoo-user] convert rpm to ebuild

[Öhler, Alessandro]

Hi

I follow this treat now for a while, but something is still missing here.

RPM is not just a Binary Package. I agree most of them are.
Some of the RPM´s also have some scripts embedded which are not handled if you convert it with  rpm2targz or simular.

For example i still look for an way to convert Legate Networker RPM´s to Gentoo Ebuild without manual extracting those scripts which are normaly handled at installtime by the RPM System :-(.


------------------http://www.rpm.org/max-rpm/s1-rpm-inside-scripts.html-------------
Install/Erase-time Scripts

The other type of scripts that are present in the spec file are those that are only used when the package is either installed or erased. There are four scripts, each one meant to be executed at different times during the life of a package:

    *

      Before installation.
    *

      After installation.
    *

      Before erasure.
    *

      After erasure. 
-----------------------------------------------------------------------------------

By the way does someone have an idea how this can be done easily without extracting them manualy ??


Building an Binary Gentoo Ebuild from just Binary RPM´s no problem so far, but if those scripts needed for installation, the hard life goes on.

Ciao

	Alessandro





-----Original Message-----
From: Neil Bothwick [mailto:neil@digimed.co.uk] 
Sent: Freitag, 11. Mai 2007 12:35
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] convert rpm to ebuild

On Fri, 11 May 2007 13:25:46 +0300, Nistor Andrei wrote:

> > That won't work, emerge can only work with ebuilds or portage binary 
> > packages. You can either write your own ebuild to install the 
> > binary, which is pretty straightforward, or simply unpack it to /.
> >  
> Portage binary packages aren't actually .tar.gz archives?

No, they are tar.bz2 archives with some metadata appended. without that metadata, portage cannot create an entry in the package database.


--
Neil Bothwick

Life is pleasant. Death is peaceful. Its the transition thats troublesome. - Isaac Asimov
Die Information in dieser Nachricht ist vertraulich und ausschliesslich fuer den Adressaten bestimmt. Der Empfaenger dieser Nachricht, der nicht der Adressat, einer seiner Mitarbeiter oder sein Empfangsbevollmaechtigter ist, wird hiermit davon in Kenntnis gesetzt, dass er deren Inhalt nicht verwenden, weitergeben oder reproduzieren darf. Sollten Sie diese Nachricht irrtuemlich erhalten haben, benachrichtigen Sie uns bitte unverzueglich per Telefon und retournieren Sie uns die Nachricht per E-Mail/Fax.


The information contained in this e-mail is privileged and confidential and is for the exclusive use of the addressee. The person who receives this e-mail and who is not the addressee, one of his employees or an agent entitled to hand it over to the addressee, is informed that he may not use, disclose or reproduce the contents thereof. If you have received this communication by mistake, please let us know by telephone without delay and send it back to us by e-mail/fax.
--
gentoo-user@gentoo.org mailing list