Re: [Linuxcoe-devel] DiStRo nAmInG and code reliance

[Bruno C. <Bru...@hp...>]

Bryan Gartner said on Mon, Feb 23, 2009 at 08:52:09AM -0700:

> My current plan is to create all of our items using lsb_release -a output
> as the standard.  

Interesting. On my Mandriva distro it gives:

LSB Version:    lsb-3.1-amd64:lsb-3.1-noarch:*
Distributor ID: MandrivaLinux
Description:    Mandriva Linux 2009.0
Release:        2009.0
Codename:       zarapha

However, the lsb package is optional on most distro. And then, it uses
.etc.distro-release, except on Debian where it doesn't exist ;-)

Interesting to see that I arrived at a similar solution, but not
requiring the lsb package to be present in my pbdistrocheck package.
I'll submit it to CPAN now that I have an account BTW.

$ pbdistrocheck
distro tuple: mandriva,2009.0,md,rpm,.mdv2009.0,sudo urpmi.update -a ; sudo urpmi --auto

>         Since we already did a 4.1 "release" (almost one year ago) and
> 	a set of packages, I'll rev the current HEAD to tag v4_2 and do
> 	another set of tar.gz/packages (using Bruno's project-builder),
> 	then move HEAD to start generating 4.3 for all the upcoming
> 	snapshots/work.

Feel free to ask for help in your pb setup. You're my most advanced user
(at least I think ;-) so I want that it goes smoothly for you.

Bruno.
-- 
Linux Profession Lead EMEA  / Open Source Ambassador \   EMEA CME SoL. Center
http://www.mondorescue.org / HP/Intel Solution Center \  http://hpintelco.net
Des infos sur Linux?  http://www.HyPer-Linux.org      http://www.hp.com/linux
La musique ancienne?  http://www.musique-ancienne.org http://www.medieval.org