[FGS] Postgis and postgresql installed

Frank Warmerdam warmerdam at pobox.com
Thu Jun 24 12:43:23 EDT 2004

Tyler Mitchell wrote:
>>I realize I haven't been to specific about this, but my theory is that
>>for each FGS package that will be related as it's own .tar.gz file 
>>thereshould be a subdirectory under /home/fgs/fgs-pkgs.  So, for 
>>instance, one for
>>postgres+postgis, and one for Python.   
> Sounds good to me, Frank.  Tell us more about your ideas, I'm sure it's more thought out than mine :)  Once I know more, then I'll update the packages I started.  If I'm tracking you correctly is just means dropping the .../dev/... that I've been using so it installs into ../fgs-pkgs/<product name>/ instead.


OK, I wrote up a couple topics making some of my approach more concrete.  This
is all open to discussion of course.  The really key issue is that each fgs
pacakge builder ends up with compatible .tar.gz files in the staging area by
whatever means.


>>I'm not sure that we need a package for
>>GTK.  I am expecting we would either distribute GTK 1.x in the 
>>base package if it is used by multiple packages, or just in the openev package 
>>if that is the only thing that uses it.
> We plan to use GTK with the Lifeline/Xaya application that Mishtu, I and others 
 > are building.  However, we are also hoping to tie it into OpenEV.  So I'm not
 > sure what we'll want to do, but it would be nice to compartmentalize these
 > dependencies IMO.

Are you planning to build that on top of OpenEV or side-by-side?  If it is
distinct from OpenEV then you might be best off working against GTK2.  If
you are building on OpenEV then you might as well just use the same GTK1
used by OpenEV, and in fact have OpenEV as a prereq of your the Lifeline/Xaya
package with gtk1 embedded in it.

I personally would like to avoid having too fine a granularity on the
packages.  I don't want people to find they need to install five or ten packages
just to get one particular thing working.  For instance, to install OpenEV
I am hoping I would just have to install fgs-base and fgs-openev, possibly
throwing in fgs-python to ensure I get a compatible python.

Best regards,

I set the clouds in motion - turn up   | Frank Warmerdam, warmerdam at pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush    | Geospatial Programmer for Rent

More information about the Foss-gis-suite mailing list