From: "C. Brewer" <cbrewer@stealthaccess.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] SuSE Kernel Sources
Date: Fri, 3 Oct 2003 00:20:45 -0700 [thread overview]
Message-ID: <20031003002045.3ef71d4e.cbrewer@stealthaccess.net> (raw)
In-Reply-To: <20031003063019.GA11505%chutz@gg3.net>
[-- Attachment #1: Type: text/plain, Size: 461 bytes --]
True, there were solid suggestions in the bug, but IIRC most of them
revolved around rpm/rpm2cpio, negating the need for rpm2tgz in the first
place. Maybe I ( or someone with the time) will work out the hitch in
rpm2tgz. IMHO its bad enough needing to install rpms in the first place,
without adding the rpm program as well. Just a thought:)
--
Chuck Brewer
Registered Linux User #284015
Get my gpg public key at pgp.mit.edu!! Encrypted e-mail preferred.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-10-03 7:20 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
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 [this message]
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=20031003002045.3ef71d4e.cbrewer@stealthaccess.net \
--to=cbrewer@stealthaccess.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