Localconfig Tool

[Kevin Benton]

Hi all.  I am considering writing a localconfig maintenance tool but
wanted to get input from everyone before doing it.  Why a tool for the
localconfig?  I don't want brand-spanking-new admins messing around with
the code in a way that could take down BZ for the enterprise.  I also
want to make sure there are backups and a history of changes.  We're
tracking 34 different OS / version combinations before we start counting
the many Linux variants, and updates are routinely made monthly. 
Obviously, it makes a lot of sense to write this tool.  I also don't
want to collide with what's happening with BZ.  My desire would be that
BZ would move the configuration of the OS's to the DB rather than
leaving it in localconfig.  It would also be my desire that OS and OS
Version be separate items.

*** CAUTION: This may start a flame war which is clearly not my goal ***

I haven't made up my mind yet on whether or not I would write this tool
in Perl or PHP if I write it, however, because of the ease of writing it
in PHP, I'm leaning more that way though I am considering the challenge
of a lone PHP program in the middle of a Perl package.  Knowing both PHP
and Perl, I have wondered if this group has considered moving toward PHP
instead of Perl.  I like Perl, but for web-based scripting, I personally
prefer PHP hands down.


-- 
Kevin Benton <kevin.benton at amd.com>
AMD Longmont