public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Fabian Groffen <grobian@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: lzma tarball usage
Date: Wed, 7 May 2008 15:34:30 +0200	[thread overview]
Message-ID: <20080507133430.GI15536@gentoo.org> (raw)
In-Reply-To: <1210166592.19574.10.camel@localhost>

On 07-05-2008 16:23:12 +0300, Mart Raudsepp wrote:
> This is a plea and also a request for comments on the matter of
> using .tar.lzma tarballs or not, and for what packages this is
> acceptable and for what not.

Just as a little background:
GNU chose to switch from bzip2 to lzma, for it produces smaller files
(less bandwith) and decompresses faster.

They no longer provide the bzip2 versions of archives for newer releases
IIRC, so it's either tar.gz or tar.lzma.

> I'd be happy if some other unpacker is used than lzma-utils - one that
> does not depend on libstdc++ - I'm sure it can be done, heck it's done
> in integrated form in some other projects in less than a couple
> kilobytes of code for the unpacking from a VFS. Meanwhile please
> consider using the upstream provided .tar.gz tarballs instead and not
> roll patchsets in .lzma just cause you can.

See above why it might not just be "'cause you can".

> coreutils and linux-headers come to my mind out of system packages right
> now. I'm sure more dragons await me.

m4, that one gave me some headaches, because lzma-utils required some
eautoreconf, which introduced a nice cycle.


-- 
Fabian Groffen
Gentoo on a different level
-- 
gentoo-dev@lists.gentoo.org mailing list



  reply	other threads:[~2008-05-07 13:35 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-07 13:23 [gentoo-dev] RFC: lzma tarball usage Mart Raudsepp
2008-05-07 13:34 ` Fabian Groffen [this message]
2008-05-08 18:45   ` Mart Raudsepp
2008-05-08 19:09     ` Fabian Groffen
2008-05-08 19:17       ` Santiago M. Mola
2008-05-08 19:21       ` Mart Raudsepp
2008-05-17 15:55     ` Enrico Weigelt
2008-05-10  7:32   ` Mike Frysinger
2008-05-10  7:36     ` Fabian Groffen
2008-05-10  9:57       ` Mike Frysinger
2008-05-07 14:12 ` Natanael Copa
2008-05-07 14:55   ` Ulrich Mueller
2008-05-08  8:06     ` [gentoo-dev] " Duncan
2008-05-08 10:49       ` Diego 'Flameeyes' Pettenò
2008-05-08 10:59         ` Graham Murray
2008-05-08 11:31           ` Diego 'Flameeyes' Pettenò
2008-05-08 11:41         ` Ulrich Mueller
2008-05-07 14:53 ` [gentoo-dev] " Benedikt Morbach
2008-05-07 15:03   ` Ulrich Mueller
2008-05-07 15:02 ` Benedikt Morbach
2008-05-07 16:06 ` Chris Gianelloni
2008-05-07 18:38 ` Enrico Weigelt
2008-05-07 20:01   ` Richard Freeman
2008-05-07 20:10     ` Doug Goldstein
2008-05-08  0:52 ` [gentoo-dev] " Ryan Hill
2008-05-08 13:17   ` Doug Goldstein
2008-05-08 13:28     ` Ciaran McCreesh
2008-05-08 13:32       ` Doug Goldstein
2008-05-08 13:36         ` Ciaran McCreesh
2008-05-08 13:43           ` Doug Goldstein
2008-05-09  8:37             ` James Cloos
2008-05-08 14:30           ` Diego 'Flameeyes' Pettenò
2008-05-08 13:41         ` Doug Goldstein
2008-05-08 14:33           ` Robert Buchholz
2008-05-09  1:04     ` Ryan Hill
2008-05-08 11:30 ` [gentoo-dev] " Luca Barbato

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=20080507133430.GI15536@gentoo.org \
    --to=grobian@gentoo.org \
    --cc=gentoo-dev@lists.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