[Bio-linux-dev] upgrade_to_8.sh

[Tim Booth]

Hi Steve,

The lsb_release think makes the most logical sense, but what I couldn't
work out was what this would be set to on a partially upgraded system,
or one upgraded without using the official upgrade tool.  Does it get
set at the start of the upgrade or at the end or in the middle?

To be honest I can't really remember my rationale when I wrote the
upgrade_to_7 script, and my method is probably not the best, but since
it seemed to work well I just decided to stick with it for the
upgrade_to_8 script.  If people report problems I'll change it.

Cheers,

TIM

On Sun, 2014-08-03 at 22:09 +0100, Steve Moss wrote:
> Dear Tim,
> 
> 
> I was looking through the upgrade_to_8.sh script and noticed you use
> the PYVERS function to check the version of the operating system. I
> wondered what the rationale was behind that? Could there be any cases
> where people who upgrade their python version pre-14.04 pass the test
> for 14.04 when they shouldn't?
> 
> 
> Had you thought about checking /etc/debian_version instead? Precise
> lists wheezy/sid, where as Trusty lists jessie/sid. You could also
> parse the output of lsb_release - d? e.g. lsb_release -d | cut -d " "
> -f 2 gives 14.04.1.
> 
> 
> Cheers,
> 
> 
> Steve
> -- 
>  
> Steve Moss
> about.me/gawbul
> Steve Moss on about.me
>  

-- 
Tim Booth <tbooth at ceh.ac.uk>
NERC Environmental Bioinformatics Centre 

Centre for Ecology and Hydrology
Maclean Bldg, Benson Lane
Crowmarsh Gifford
Wallingford, England
OX10 8BB 

http://nebc.nerc.ac.uk
+44 1491 69 2705