| 1 |
On Thu, 2007-05-10 at 22:29 +0200, Bo Ørsted Andresen wrote: |
| 2 |
> On Thursday 10 May 2007 22:16:59 Florian Philipp wrote: |
| 3 |
> > |
| 4 |
> > 1. This page provides no way to handle a binary-only rpm, just sources. |
| 5 |
> > Yet, sources are no problem since they should be available as a tarball or |
| 6 |
> > in portage itself while rpms of proprietary closed-source software are |
| 7 |
> > quiet common. I could transfer them into a .deb-archive using "alien" which |
| 8 |
> > leads me to problem number 2 ... |
| 9 |
> |
| 10 |
> There are plenty of ebuilds for binary only packages in the tree. The above |
| 11 |
> link helps you to unpack the binary files to $WORKDIR. After that you can use |
| 12 |
> the install functions [1] (or cp or whatever) in src_install() to install |
| 13 |
> to the image ($D). And perhaps you need and env.d file or whatever else may be |
| 14 |
> missing (for additions to *PATH variables). |
| 15 |
> |
| 16 |
> When all of that is done you can emerge it. And no, a .deb isn't any better. |
| 17 |
> |
| 18 |
> [1] http://devmanual.gentoo.org/function-reference/install-functions/index.html |
| 19 |
> |
| 20 |
|
| 21 |
One example from the tree is media-video/realplayer. It is a package |
| 22 |
that installs a binary package from an rpm. |
| 23 |
|
| 24 |
Regards, |
| 25 |
Paul |
| 26 |
-- |
| 27 |
gentoo-user@g.o mailing list |
Archives