| 1 |
2014-02-20 8:19 GMT-07:00 Mike Gilbert <floppym@g.o>: |
| 2 |
> On Thu, Feb 20, 2014 at 8:12 AM, Lars Wendler <polynomial-c@g.o> wrote: |
| 3 |
>> Hi, |
| 4 |
>> |
| 5 |
>> it seems like some GNU projects start to release their source tarballs |
| 6 |
>> in lzip compressed versions only [1][2]. |
| 7 |
>> This is a problem since portage's unpack function doesn't know anything |
| 8 |
>> about lzip. |
| 9 |
>> |
| 10 |
>> ... |
| 11 |
>> |
| 12 |
>> What do you think? |
| 13 |
>> |
| 14 |
> |
| 15 |
> A short-term solution would be to add lzip support to unpacker.eclass |
| 16 |
> and utilize that instead of the built-in unpack function. |
| 17 |
I had the same idea: |
| 18 |
<https://bugs.gentoo.org/show_bug.cgi?id=501912> |
| 19 |
|
| 20 |
> |
| 21 |
> A long-term solution would be to modify PMS to support unpacking lzip archives. |
| 22 |
I don't see, why we should do that. unpacker.eclass is a good place to |
| 23 |
support exotic archive formats. |
| 24 |
|
| 25 |
> |
| 26 |
> Either way, you will still need to have app-arch/lzip in DEPEND, |
| 27 |
> similar to app-arch/unzip. |
| 28 |
Or use $(unpacker_src_uri_depends). |
| 29 |
|
| 30 |
> |
| 31 |
|
| 32 |
|
| 33 |
|
| 34 |
-- |
| 35 |
Christoph Junghans |
| 36 |
http://dev.gentoo.org/~ottxor/ |
Archives