From: Georgi Georgiev <chutz@gg3.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] new rpm.eclass
Date: Sun, 22 Jun 2003 09:12:38 +0900 [thread overview]
Message-ID: <20030622001238.GB17932%chutz@gg3.net> (raw)
In-Reply-To: <1056205815.8266.20.camel@mcvaio.liquidx.net>
[-- Attachment #1: Type: text/plain, Size: 1442 bytes --]
On 21/06/2003 at 15:30:19(+0100), Alastair Tse used 1.4K just to say:
> Hi All,
>
> There are a number of packages that require us extracting directly from
> RPMs or Source RPMs. As a result, a number of ebuilds depend on
> rpm2targz (a slackware creation) for extraction and have their own
> src_unpack routine.
>
> To automate the process a little better, I've written an rpm.eclass
> which is a slot in replacement for src_unpack(). It automatically
> extracts rpm packages and for source rpms, it also extracts inner
> tarballs. Internally, it still uses rpm2targz but is a little smarter
> about cleaning up after itself and handles multiple sources properly.
>
> This is now in portage. For an example of how it can used, look at
> app-misc/jot or x11-themes/redhat-artwork.
The rpm.eclass uses the rpm2targz script itself which is a waste of time and
resources. Please take a look at bugs 23249 and maybe 23179 for another
approach which was already adopted by a few packages (ccc, cxx, libcpms,
libcxml, ladebug and compaq-sources) even before the bug was submitted.
--
/^^^^^^^^^^^^^^^^^^^^^^^^^^^\/^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\
/ Georgi Georgiev (-< / I cannot and will not cut my \
\ chutz@chubaka.net /\ .o)\ conscience to fit this year's /
/ +81(90)6266-1163 V_/_ |(/)/ fashions. -- Lillian Hellman \
\___________________________/\__________________________________/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-06-22 0:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-21 14:30 [gentoo-dev] new rpm.eclass Alastair Tse
2003-06-22 0:12 ` Georgi Georgiev [this message]
2003-06-22 12:27 ` 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=20030622001238.GB17932%chutz@gg3.net \
--to=chutz@gg3.net \
--cc=chutz-dated-1057450359.dfc3b6fa6230@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