[FGS] Preliminary packaging

[Tyler Mitchell]

> My plan is that we should have a wiki page for each package with some 
notes
> about it.  They should all be linked off the Fgs.FgsTools page at:
> 
>    http://harmeny.com/twiki/bin/view/Fgs/FgsTools

Great start!

> The idea (in my thinking) is that the end user could untar the .tar.gz 
files
> for various packages (ie. base, mapserver) under one "tree" such as in
> /usr/local and they would overlay each other.  Then they just need to 
set
> LD_LIBRARY_PATH, PATH, PYTHONPATH and perhaps a few other things to 
point
> to the new tree.

That sounds really good to me and fits with what my desire has been.

> I see the machine has python 2.3 installed so I think that can be our 
"target"
> python distribution.  I haven't tried packaging the python itself up 
though
> eventually we should.

You did this for openev_fw, but was that only windows?  That would at 
least be a good template for modules to use, etc.

> I have tried the base "package" as it exists now, and found it does 
> not work on
> my old debian system due to a dependency on GLIBC_2.3.  I can't helpbut 
wonder
> if we would be better off building our packages on an older system so we
> depend on an older version of GLIBC but there isn't much to be done 
about
> that for now.  We will have to keep an eye on the GLIBC issue and see 
how
> we need to react.

Can you give us a brief summary of the env settings you set so we can test 
it out too.
I assume it worked okay on maxine.

Tyler