public inbox for gentoo-python@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Gilbert <floppym@gentoo.org>
To: gentoo-python@lists.gentoo.org
Subject: [gentoo-python] Re: [PATCH] eselect-python: update and clean the live ebuild up.
Date: Thu, 1 Nov 2012 14:47:47 -0400	[thread overview]
Message-ID: <CAJ0EP40xe7BvGQg60VuiMg1ASDZh=CMNFUvenaLOovBZshNy9g@mail.gmail.com> (raw)
In-Reply-To: <CAJ0EP40syd5=xSkB2_AAUvLERfdmL3meNhhQCjbTvVW5xec03Q@mail.gmail.com>

On Thu, Nov 1, 2012 at 12:27 PM, Mike Gilbert <floppymaster@gmail.com> wrote:
> On Thu, Nov 1, 2012 at 5:50 AM, Michał Górny <mgorny@gentoo.org> wrote:
>> First of all, it didn't work at all (lacked SVN unpack commands). Since
>> eselect-python has been migrated to git, I have replaced the SVN code
>> with git one as well.
>>
>> Secondly, I have set 'eselect python update' commands to run
>> unconditionally, and added '--if-unset'. This doesn't hurt and should
>> handle any future updates and fixing broken systems (as in, if user
>> breaks python symlinks, he just needs to reinstall eselect-python).
>>
>> Thirdly, I have split 'eselect python update' into '--python2'
>> and '--python3' parts. This will ensure that both python2 & python3
>> implementation will be kept sane (and the active one will update
>> the main interpreter as well).
>
> Let's have releng test this patch; the pkg_postinst changes might
> cause some issue for stage building.
>
> Otherwise, looks fine.

I sent the above reply from the wrong address, so just re-sending to the list.


      parent reply	other threads:[~2012-11-01 18:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-01  9:50 [gentoo-python] [PATCH] eselect-python: update and clean the live ebuild up Michał Górny
     [not found] ` <CAJ0EP40syd5=xSkB2_AAUvLERfdmL3meNhhQCjbTvVW5xec03Q@mail.gmail.com>
2012-11-01 18:47   ` Mike Gilbert [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJ0EP40xe7BvGQg60VuiMg1ASDZh=CMNFUvenaLOovBZshNy9g@mail.gmail.com' \
    --to=floppym@gentoo.org \
    --cc=gentoo-python@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox