[fdo-internals] Hosting FDO 3.5 builds / Binaries for CentOS and Ubuntu

Jason Birch jason at jasonbirch.com
Thu Feb 18 10:11:50 EST 2010

I'd suggest that if you're installing under osgeo (which makes sense
to me) that you drop the "opensource" part of "mapguideopensource" as
we have on the windows installer.


On 2010-02-17, Trevor Wekel <trevor_wekel at otxsystems.com> wrote:
> Hi Traian,
> I am mostly interested in the binary installer.
> Most Linux distributions adhere to the Unix Filesystem Hierarchy Standard
> (FHS) http://proton.pathname.com/fhs/.  According to the standard,
>> The /usr/local hierarchy is for use by the system administrator when
>> installing software
>> locally. It needs to be safe from being overwritten when the system
>> software is updated. It
>> may be used for programs and data that are shareable among a group of
>> hosts, but not found in
>> /usr.
>> No other directories, except those listed below, may be in /usr/local
>> after first installing a > FHS-compliant system.
> So building and then installing Fdo to /usr/local is probably ok but
> installing to /usr/local/fdo-3.5.0 seems to violate the standard.  Using a
> package manager under /usr/local seems a bit dicey.
> /opt may be more appropriate.  According to the standard,
>> /opt is reserved for the installation of add-on application software
>> packages.
>> A package to be installed in /opt must locate its static files in a
>> separate /opt/<package> or
>> /opt/<provider> directory tree, where <package> is a name that describes
>> the software package > and <provider> is the provider's LANANA registered
>> name.
>> Package files that are variable (change in normal operation) must be
>> installed in /var/opt.
>> Host-specific configuration files must be installed in /etc/opt.
> So both /opt/fdo-3.5.0 and /opt/osgeo/fdo-3.5.0 would be legal from a
> directory usage standpoint.  The /var/opt and /etc/opt requirements would
> make MapGuide installs more complicated but would not affect Fdo
> installation.  Maybe we just "ignore" those rules for now and do some
> additional fix up when time permits.
> Actually I think /opt/osgeo/fdo-3.5.0 might be better choice because it
> leads logically to /opt/osgeo/mapguideopensource-2.2.0 and may also allow
> simultaneous installation of major releases and service packs.  For
> example:
> /opt/osgeo/fdo-3.5.0 with /opt/osgeo/mapguideopensource-2.2.0  (initial
> release)
> /opt/osgeo/fdo-3.5.2 with /opt/osgeo/mapguideopensource-2.2.1  (sp2 for Fdo,
> sp1 for MapGuide)
> /opt/osgeo/fdo-3.6.0 with /opt/osgeo/mapguideopensource-2.3.0  (next major
> release)
> Regards,
> Trevor
> _______________________________________________
> fdo-internals mailing list
> fdo-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/fdo-internals

More information about the fdo-internals mailing list