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

[Bryan G. <bry...@hp...>]

Bruno,

On Mon, Feb 23, 2009 at 04:44:06PM +0000, Cornec, Bruno (Open Source and Linux Technology Architect) wrote:
> > 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 ;-)

Actually I mean that I'll "name" all of our config files according
to this "standard", not that I'll actually run lsb_release on the
LinuxCOE SystemDesigner host nor on any target (designed) system.

My proposed naming guideline will be:

	<lsb_release -s -i>-<lsb_release -s -r>-<uname -m>
         Distributor ID    - Release           - machine hardware name

since all the LSB supported distros will have to have that namespace
already approved/vetted.  Sure I'll have to deal with those
distributions that don't deliver lsb_release, but certainly for the
set we are supporting that will be a small exception set basis (since
all already do).

> 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

Good that you ended up in a similar state.  But at this point I have no
need to distribute *any* tool to calculate this, but only to run it once
on a given "tuple" to generate what should be used.  If we do later
get to this point, perhaps when we migrate to using something like
Config::Model, it would be important to calculate a value (perhaps
via the pbdistrocheck) and generate all the config files automatically.

> >         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.

You know I will.  I am still having some fundamental startup questions,
adjusting .pbrc values to the appropriate settings, and also doing first
run kinds of cms2build operations (from scratch).  I'll contact you
directly with these questions,

bryang