From: Georgi Georgiev <chutz@gg3.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] SuSE Kernel Sources
Date: Fri, 3 Oct 2003 10:58:53 +0900 [thread overview]
Message-ID: <20031003015853.GA7332%chutz@gg3.net> (raw)
In-Reply-To: <004f01c38950$5177f1b0$8000a8c0@1d36l>
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.
--
(* Georgi Georgiev (* Get in touch with your feelings of hostility (*
*) chutz@gg3.net *) against the dying light. -- Dylan Thomas *)
(* +81(90)6266-1163 (* [paraphrased periphrastically] (*
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-10-03 1:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-03 1:47 [gentoo-dev] SuSE Kernel Sources Paul Varner
2003-10-03 1:58 ` Georgi Georgiev [this message]
2003-10-03 2:30 ` Paul Varner
2003-10-03 4:17 ` C. Brewer
2003-10-03 6:30 ` Georgi Georgiev
2003-10-03 7:20 ` C. Brewer
2003-10-03 13:15 ` Georgi Georgiev
2003-10-03 17:57 ` C. Brewer
2003-10-04 4:14 ` Georgi Georgiev
2003-10-03 15:10 ` Alastair Tse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031003015853.GA7332%chutz@gg3.net \
--to=chutz@gg3.net \
--cc=chutz-dated-1066355935.de00cc9ef3b1@gg3.net \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox