-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 09/27/2012 05:23 AM, Piotr Szymaniak wrote:
> On Wed, Sep 26, 2012 at 01:43:27PM -0700, Matt Turner wrote:
>> On Wed, Sep 26, 2012 at 1:30 PM, Michael Mol <mike...@gmail.com> wrote:
>>> A few months ago, I filed bug 423651 to ask that bzip2 on the install
>>> media be replaced with
>>>  pbzip2. It was closed a short while later, telling me that it'd
>>> involve changing what's kept in @system, and that had to be discussed
>>> here, rather than in a bug report.
>>
>> If we're going to ship a parallel bzip2 implementation, it should be
>> lbzip2 and not pbzip2.
>>
>> lbzip2 can decompress bz2 archives with multiple threads that haven't
>> been compressed with lbzip2/pbzip2.
> 
> Afair I'm using PORTAGE_BZIP2_COMMAND with lbzip2 and it works fine.
> Also some time ago I've changed a bit the (famous?) stage4 backup
> script from g-wiki to support parallel gz/bz2 implementations (simple
> check if there pbzip2/lbzip2/foobar installed and if yes, use it instead
> of normal gzip/bzip2).

I've been testing PORTAGE_BZIP2_COMMAND=lbzip2 for the few weeks since
this thread as well, and I have to say it's been great.
> 
> Maybe portage should be like my stage4 mod? If it finds some parallel
> (de)compressor it should use it, if not fallback to standard gzip/bzip2?

The releng team has begun using lbzip2 for decompressing things as much
as possible for speeding up catalyst builds, and speaking only for
myself I think it's been useful.  I spoke to zmedico about replacing the
default portage decompresser and he suggested far more use could be
attained by simply creating an eselect-bzip2 (possibly defaulting to
lbzip2 as this thread seemed to agree).  I'm confident no one would
attempt to block my adding eselect-bzip2 to the tree (aside from my poor
coding skills), but would anyone be interested in blocking using lbzip2
by default?  It seems pretty safe and I've done dozens of full system
builds etc.

Thanks,
Zero_Chaos
> 
> 
> Piotr Szymaniak.
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iQIcBAEBAgAGBQJQjo79AAoJEKXdFCfdEflKQNQQAIur3Mx4eD6kVv3US6kDkKpn
Z8aHyZqWIOws9VqcPCJUb1c1bn8aj2QTjL63obh//rJby1Qd1P3X3OA9hKfaiyiJ
hbgWRu5RkMSNPIdXhaslD3h/kL78BPr9eVz9O3R/TMp01puz4su0j1JVOtAT5Ny2
qAVof+H6RC5aCP2pKjIkvDq9vma/jd9QT98rM3UIw3BorBpkl0vTTa+sLtGA+U6p
mBkYZJFUUnkW3AtNC1ucPvQS9a7NwOxH5EDGEy4QeSJh9nvQZ8zCFivNtr4SUS6A
SGV0j/PB0Uqf42y1NOBfFSEQoQGT3aIlZzkbGdJKf6/jIdGPHhxWt3npQ6U6gOg9
TA/8zCJkJk0GZKAIq+K/y8STczeuIJ2hgrHUup4/I6CYwI66eBRiqnayNEmah7Cy
rpqR7xwqh+F2JrjljNYfE9qVQKwqhLU5MsOONlqRS+FPw+SuxxbJM6BiLCk4s0Qz
GPs5PXTz92MzzQ18XUuMq53bi9IaEmJJa8E83IBm3PD4zq67KsiWd2YxQo/JYX4p
ZTBayLabbY6PRwMVx0k9jKG7aOOKFZ5t2k5BmZDv6JBD2Sww9q6+xUPoTDwsZPgZ
pVv2m3AwaOXbGpvMrpqmzOTxbovUALp9WhdyTxlR5NmbTeXIuaKW/lQTU0cl/LKP
ACg4IADjv3hQz7gfsHAP
=hCz9
-----END PGP SIGNATURE-----

Reply via email to