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?
pgpkdWwJwt2du.pgp
Description: PGP signature
