public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Georgi Georgiev <chutz@gg3.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] SuSE Kernel Sources
Date: Fri, 3 Oct 2003 22:15:37 +0900	[thread overview]
Message-ID: <20031003131536.GD12607%chutz@gg3.net> (raw)
In-Reply-To: <20031003002045.3ef71d4e.cbrewer@stealthaccess.net>

[-- Attachment #1: Type: text/plain, Size: 1778 bytes --]

On 03/10/2003 at 00:20:45(-0700), C. Brewer used 1.0K just to say:
> 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.

The reason I opened that bug in the first place, is because I didn't want to
compile rpm to install icc on a friend's computer. So even though rpm/rpm2cpio
negates the need for rpm2tgz, there is a solid reason why we do need a quick,
easy, small solution for uncompressing rpms.

1. feature(gzip + bzip2 + rpmoffset) == feature(rpm2cpio)

2. size(gzip + bzip2 + rpmoffset) <<<<<< size(rpm2cpio) == size(rpm)

> Maybe I ( or someone with the time) will work out the hitch in
> rpm2tgz.

What hitch? We've alrady worked around that hitch. However if you read the bug
correctly -- there was a suggestion for fixing the rpm2tgz package itself, but
Mr.Tse decided to simply fix the rpm.eclass. Which IMHO is a solution good
enough as we mostly need to uncompress RPMs in ebuilds.

> IMHO its bad enough needing to install rpms in the first place,
> without adding the rpm program as well. Just a thought:)

It is *not* a bad idea, and here is why:

First of all, Gentoo does not "install" rpms. Gentoo doesn't care about
dependency information in the rpm, nor does it need to update some freaky
database that rpm uses. It only needs the files. So in Gentoo terms -- the RPM
package is just a freaky tarball. Why would I need the rpm package to
uncompress that freaky tarball if I can go without it?

-- 
\    Georgi Georgiev   \  QOTD: "Everything I am today I owe to        \
/     chutz@gg3.net    /  people, whom it is now to late to punish."   /
\   +81(90)6266-1163   \                                               \

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-10-03 13:15 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
2003-10-03 13:15           ` Georgi Georgiev [this message]
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=20031003131536.GD12607%chutz@gg3.net \
    --to=chutz@gg3.net \
    --cc=chutz-dated-1066396540.9d8df69bedec@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