[Systers-dev] Additional Development Server

[Gloria W]

> On Mon, Mar 29, 2010 at 8:11 PM, Kathy Richardson<kjr at casaveracruz.com>wrote:
>
>    
>> Question about MM 3.0 environment:  Is that all going to be on Ubuntu 9.1
>> with the latest python, etc?
>>
>>      
> We need to stick with the Ubuntu LTS series since those releases are best
> for production servers given the long-term package support.  However, 10.04
> LTS is coming out in mid-April so we could think about moving from 8.04 LTS
> to 10.04 LTS.  We are probably going to want to stick with Python 2.5 - but
> 10.04 LTS might have Python 2.6 as the default so we'd need to do some
> research.  It's always possible to install multiple versions of Python.
>    
true, but IMHO, and from first-hand experienc,e it is a royal pain to 
use debian to manage this. For example, if you install another version 
of Python and configure Debian to use it as the unsupported default, it 
will _still_ replace it with Python 2.5 if other python-dependent OS 
tools are installed (such as denyhosts).

So I recommend this fool-proof way of installing different versions of 
Python. It is the old-timer, "AT&T" way, which has never failed, and is 
mutually exclusive of any OS dependencies.

Build and install Python 3.X in /usr/local/python/3.X (very easy if you 
download the source, and pass the "--prefix=/usr/local/python/3.X" to 
the "configure" command).

Set every developer's .bash_profile to prepend /usr/local/python/3.X/bin 
to the PATH variable (I am afraid to do this in .bashrc, because it can 
run multiple times per session, meaning your path may grow indefinitely. 
The trade-off is that you have to make sure the .bash_profile is 
executed when people log in, which is not always the case in bash. This 
is usually done in the master /etc/profile, for all users other than root).

Do we want to apply this to the dev image?

Gloria
> Jen
>
>
> To unsubscribe from this conversation, send email to<systers-dev+development3+unsubscribe at systers.org>  or visit<http://systers.org/mailman/options/systers-dev?override=85&preference=0>
> To contribute to this conversation, use your mailer's reply-all or reply-group command or send your message to systers-dev+development3 at systers.org
> To start a new conversation, send email to<systers-dev+new at systers.org>
> To unsubscribe entirely from systers-dev, send email to<systers-dev-request at systers.org>  with subject unsubscribe.
>
>