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

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

FYI,

On Mon, Feb 23, 2009 at 11:39:26AM +0000, Mayes, Lee wrote:
> Gartner, Bryan W wrote:

> >>> So, I was wondering about this possibility.  In the code, should we perhaps
> >>> do all our checks as "DISTRO" or maybe "distro" and then frontend all of
> >>> our parsing with the respective toupper or tolower functions to be as
> >>> liberal with inputs, and strict with outputs?
> >>>       
> >> Applause !!! THat would help me a lot in what I'm trying to do outside
> >> of LinuxCOE and hopefully inside soon.
> >>
> >> As an old-time Unix user, I'm inclined towards lc myself, but I don't
> >> care as long as we can standardize on a single one and use it everywhere
> >> ! We could even consider using that distro-release file under /etc to
> >> get more info (except for Ubuntu which decided to not create one :-()

My current plan is to create all of our items using lsb_release -a output
as the standard.  Within the code, Lee can make the determination regarding
upper/lower/mixed case for the checks and for the mapping.

> > As noted, I'm suggesting we accept all case(s) as input, and just
> > use one standard internally (which actually becomes immaterial to
> > most all users then.  So:
> >
> > 	Fedora
> > 	fedora
> > 	fEDORA
> > 	...
> > 	(even if not consistent across all inputs)
> >
> > would all be acceptable as configuration values.
> >
> >   
> >> Excellent initiative. Just hope it doesn't create too much problem at
> >> the code level.
> >>     
> >
> > Easy to suggest it, now will have to access/implement it,
> >
> > bryang
> >
> >   
> This is an excellent suggestion and I'd been thinking about it a little 
> since Bruno originally suggested it last year.  I'd run into a bit of a 
> 'brain freeze' on the issue, but thinking a little more and Bruno's lc() 
> nudge I think it will be easier to implement than I had originally 
> thought.   I'll see if I can get a proof of concept working real soon.
> 
> Bryan, now might be a good time for a 'snapshot' release as I expect 
> there will be many moving parts soon. :^)

Ok, here is my plan du'jour.

        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.

This will probably take me a few days to walk through and get setup
as I try to integrate project-builder into the process.  I'll reply
back here when the above is completed.

bryang