public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] python-2.7 && python-updater
Date: Fri, 25 Mar 2011 11:46:23 -0500	[thread overview]
Message-ID: <4D8CC6DF.5090204@gmail.com> (raw)
In-Reply-To: <AANLkTi=2PrssC=oRRQ0XZS3MZi3VT-32FY6Q81N7tLEA@mail.gmail.com>

Paul Hartman wrote:
> On Fri, Mar 25, 2011 at 4:37 AM, Dale<rdalek1967@gmail.com>  wrote:
>    
>> Paul Hartman wrote:
>>      
>>> On Fri, Mar 25, 2011 at 12:28 AM, Dale<rdalek1967@gmail.com>    wrote:
>>>
>>>        
>>>> And if we should set python to 2.7, should we remove python-2.6?  I don't
>>>> think we want to break something, portage in particular.  ;-)
>>>>
>>>>          
>>> I have no trace of python-2.6 on my system at this point and I'm
>>> getting along just fine with 2.7 as my active python.
>>>
>>>
>>>        
>> Out of curiosity, how long you, or someone else, been using python 2.7?  You
>> emerged a few packages with no issues so far?  I'm sort of skidish on
>> anything other than minor updates to python.  If I mess it up, portage may
>> bite me.  o_O  We all know a broken portage is not a good thing.
>>      
> For about a week or two, no problems so far.
>
> If you switch to 2.7 then run python-updater before removing 2.6, you
> should be fine. If you take a binpkg of it first you can have some
> extra peace of mind.
>
>    

I have buildpkg in make.conf.  I keep a copy of everything installed on 
here, just in case I get to stupid one day.  We all have those days right?

Thanks.

Dale

:-)  :-)



  reply	other threads:[~2011-03-25 16:48 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-25  0:11 [gentoo-user] python-2.7 && python-updater Mark Knecht
2011-03-25  0:28 ` Dale
2011-03-25  3:42   ` Amankwah
2011-03-25  4:48   ` Paul Hartman
2011-03-25  9:37     ` Dale
2011-03-25  9:50       ` Neil Bothwick
2011-03-25 13:56         ` Mark Knecht
2011-03-25 14:26           ` Neil Bothwick
2011-03-25 18:14             ` [gentoo-user] humor: " James
2011-03-25 14:33           ` [gentoo-user] " Roman Zilka
2011-03-25 16:44             ` Dale
2011-03-25 14:33       ` Paul Hartman
2011-03-25 16:46         ` Dale [this message]
2011-03-28 13:22     ` KH
2011-03-28 15:02       ` Mark Knecht
2011-03-28 15:41       ` Roman Zilka
2011-03-29  8:26         ` KH
2011-03-25 13:02   ` [gentoo-user] " Simon Siemonsma
2011-03-25 16:50     ` Dale
2011-03-25 19:09   ` [gentoo-user] " Stéphane Guedon
2011-03-25 19:21     ` Grant
2011-03-25 20:38     ` Neil Bothwick
2011-03-26 19:10       ` Mark Knecht
2011-03-26 19:22         ` Mick
2011-03-26 19:56           ` Mark Knecht
2011-03-26 20:36             ` Bill Longman
2011-03-26 20:53               ` Mark Knecht
2011-03-26 21:12                 ` Mick
2011-03-26 21:16         ` Neil Bothwick
2011-03-26 21:33           ` Mark Knecht
2011-03-26 23:06             ` Adam Carter
2011-03-27  0:44             ` Neil Bothwick
2011-03-27 15:26               ` Mark Knecht
2011-03-27 15:47                 ` Jacques Montier
2011-03-27 19:25                 ` Neil Bothwick
2011-03-27 19:50                   ` Mark Knecht
2011-03-27 20:05                     ` Neil Bothwick
2011-03-28  0:45                       ` Adam Carter

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=4D8CC6DF.5090204@gmail.com \
    --to=rdalek1967@gmail.com \
    --cc=gentoo-user@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