Re: [gentoo-dev] SuSE Kernel Sources

["Paul Varner" <gentoo-dev@varnerfamily.org>]

Georgi Georgiev wrote:
> On 02/10/2003 at 20:47:32(-0500), Paul Varner used 5.2K just to say:
>>> 1. The kernel sources are distributed by SuSE as an RPM.  The RPM
>>> data is compressed with bzip instead of gzip.  I discovered that
>>> rpm2targz doesn't understand bzipped RPM files and would not
>>> correctly process the rpm. Because of this, an explicit dependency
>>> for the kernel is the rpm ebuild. The only thing that is used from
>>> rpm is the rpm2cpio command to unpack the sources into the ebuild
>>> sandbox.  I don't use rpm in any other way.  The second dependency
>>> is cpio.  This one really isn't an issue since it is part of the
>>> system, but to be safe, I included it anyway.
>
> How did you discover that?
>
> Please check the latest version of rpm2targz, bug #23249 and the
> rpm.eclass (in reverse order). You can also take a look at the
> ebuilds for dev-lang/icc and dev-lang/ifc (the first two that come to
> mind) for hints on how to use the rpm.eclass.

I discovered it, because I used the redhat-sources ebuild as my inital
template.  When rpm2targz didn't work as expected I read through the script
to debug what it was doing. As I was stepping though the script, I saw that
it was the gunzip part that was failing, so I produced the output up to that
point and saw that I had bzipped data instead of gzipped data.
Additionally, since I saw no reason to create a tar.gz file, just to turn
around and unpack the file, I decided to use rpm2cpio directly.

Anyhow, after seeing your comments on the rpm.eclass, I know what the r1
ebuild will be using!  This is not intended as a putdown, but I have had a
hard time finding all of the information that I have been looking for to
build the ebuild.  The documentation once I find it is great, but I still
feel like I'm looking for the needle in a haystack right now. I'm sure that
it will get easier over time.

Regards,
Paul



--
gentoo-dev@gentoo.org mailing list