Re: Using "python3 setup.py" in PKGBUILDs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



On Sun, Apr 10, 2011 at 6:40 PM, Allan McRae <allan@xxxxxxxxxxxxx> wrote:
> On 11/04/11 10:48, Oon-Ee Ng wrote:
>> AFAICR users who relink python to python2 are on their own. This
>> breaks repo packages as well, not just AUR packages.
>>
>
> Correct.  This currently breaks all sort of stuff so is completely
> unsupported.

Any reason to not use "python3 setup.py" to prep for a policy allowing
for relinking in the future? If the necessary change *might* be made,
I'd rather make it now than later.

Also, I haven't found any documented policy on renaming preexisting
Python2 packages to python2-* when a Python 3 version of the package
becomes available. A consistent policy would help packagers and users.

-Aaron DeVore


[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux