[GRASS-dev] Re: [DebianGIS] build-indep for grass and other
glynn at gclements.plus.com
Mon Nov 13 03:52:33 EST 2006
> > Uhm rather confused, isn't it? I think all modules requires only
> > configuration data -> $GISBASE/etc/$MODULE_NAME
> > shared libs -> $GISBASE/lib/$MODULE_NAME
> > scripts -> $GISBASE/share/bin/scripts/$MODULE_NAME
> > arch-dep programs -> $GISBASE/bin/$MODULE_NAME/
> > arch-indep data -> $GISBASE/share/data/$MODULE_NAME
> > arch-dep data -> $GISBASE/var/data/$MODULE_NAME (maybe, not sure)
> > and so on. They could eventually and easily be remapped for FHS.
> I am not very clear on early UNIX history, but it seems that GRASS is
> using "etc/" for real "et cetera", not the unix "configuration data"
> meaning. Certainly all the stuff in $GISBASE/etc/ is miscellaneous "et
> cetera", so our naming problem is if we should rename the dir to respect
> the (slightly bizzare) unix naming convention.
> (I fully support cleaning up $GISBASE/etc/, but what to name it?)
Conventionally, programs which shouldn't be in the path go into
/usr/lib or /usr/lib/<package>. GNU added /usr/libexec with the
intention of leaving /usr/lib solely for libraries, but it hasn't
really caught on.
Glynn Clements <glynn at gclements.plus.com>
More information about the grass-dev