1 |
On Thu, Nov 1, 2012 at 12:27 PM, Mike Gilbert <floppymaster@×××××.com> wrote: |
2 |
> On Thu, Nov 1, 2012 at 5:50 AM, Michał Górny <mgorny@g.o> wrote: |
3 |
>> First of all, it didn't work at all (lacked SVN unpack commands). Since |
4 |
>> eselect-python has been migrated to git, I have replaced the SVN code |
5 |
>> with git one as well. |
6 |
>> |
7 |
>> Secondly, I have set 'eselect python update' commands to run |
8 |
>> unconditionally, and added '--if-unset'. This doesn't hurt and should |
9 |
>> handle any future updates and fixing broken systems (as in, if user |
10 |
>> breaks python symlinks, he just needs to reinstall eselect-python). |
11 |
>> |
12 |
>> Thirdly, I have split 'eselect python update' into '--python2' |
13 |
>> and '--python3' parts. This will ensure that both python2 & python3 |
14 |
>> implementation will be kept sane (and the active one will update |
15 |
>> the main interpreter as well). |
16 |
> |
17 |
> Let's have releng test this patch; the pkg_postinst changes might |
18 |
> cause some issue for stage building. |
19 |
> |
20 |
> Otherwise, looks fine. |
21 |
|
22 |
I sent the above reply from the wrong address, so just re-sending to the list. |