public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alastair Tse <liquidx@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] SuSE Kernel Sources
Date: Fri, 03 Oct 2003 16:10:40 +0100	[thread overview]
Message-ID: <1065193840.2561.6.camel@huggins.eng.cam.ac.uk> (raw)
In-Reply-To: <20031002211711.41d9210c.cbrewer@stealthaccess.net>

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

On Fri, 2003-10-03 at 05:17, C. Brewer wrote:
> because SuSe isn't the only ones to bzip2 their rpms (cant remember the
> others right off), but I bet if someone took the time to make another case
> in the script that dropped down to the bzip2 on the gzip failure, it

I believe the rpm.eclass does that for you. Another RPM that uses bzip2
compression is app-i18n/scim-chinese. It is obscure but just another
example. 

Cheers,
-- 
Alastair 'liquidx' Tse
 >> Gentoo Developer
 >> http://www.liquidx.net/ | http://dev.gentoo.org/~liquidx/
 >> GPG Key : http://dev.gentoo.org/~liquidx/liquidx_gentoo_org.asc
 >> FingerPrint : 579A 9B0E 43E8 0E40 EE93  BB1C 38CE 1C7B 3907 14F6

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2003-10-03 15:11 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
2003-10-03 17:57             ` C. Brewer
2003-10-04  4:14               ` Georgi Georgiev
2003-10-03 15:10       ` Alastair Tse [this message]

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=1065193840.2561.6.camel@huggins.eng.cam.ac.uk \
    --to=liquidx@gentoo.org \
    --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