Python distribution: switching to tar.xz

[Ruslan Mahmatkhanov]

Li-Wen Hsu wrote on 01.10.2012 22:11:
> On Mon, Oct 01, 2012 at 22:03:48 +0400, Ruslan Mahmatkhanov wrote:
>> Li-Wen Hsu wrote on 01.10.2012 21:51:
>>>
>>> EXTRACT_SUFX?= .tgz
>>> PYTHON_DISTFILE= Python-${PYTHON_PORTVERSION:S/.rc/rc/}}${EXTRACT_SUFX}
>>
>> Yes, I also bow to this option.
>>
>>> then we can define USE_XZ= yes in the ports we want to use xz
>>> distfile, which handles
>>> ${EXTRACT_SUFX} and ${EXTRACT_DEPENDS} correctly.  After python26 decommission,
>>> we can even move this into  bsd.python.mk
>>
>> python26 distributes in tar.xz too [1]. Or you meant something other?
>>
>> Ok, so I get the point. I'll prepare an patch that make ${EXTRACT_SUFX}
>> redefinable for python ports, so we can gradually switch all this ports
>> to xz. Thanks Marcus and Li-Wen.
>>
>> [1] http://www.python.org/ftp/python/2.6.8/Python-2.6.8.tar.xz
>>
>
> Oh I was not aware that, I just did not see XZ information at:
>
>     http://python.org/download/releases/2.6.8/
>
> So maybe we can simply put USE_XZ= yes in bsd.python.mk now.

So we returned to initial question :). Is this acceptable to do this, 
because it will require all the distinfos change "w/o a reason"? I 
didn't see anything criminal there, but other people may know better.

-- 
Regards,
Ruslan

Tinderboxing kills... the drives.