[GRASS-dev] Re: [DebianGIS] build-indep for grass and other issues.

Hamish hamish_nospam at yahoo.com
Mon Nov 13 00:38:27 EST 2006

> Hamish wrote:
> > 
> > how about one of these:
> >  $GISBASE/share/$MODULE_NAME/binary.app
> >  $GISBASE/support/$MODULE_NAME/binary.app
> >  $GISBASE/bin/support/$MODULE_NAME/binary.app
> >  $GISBASE/etc/support/$MODULE_NAME/binary.app
> >  $GISBASE/etc/bin/$MODULE_NAME/binary.app
> > ?
> > e.g. r.watershed's ram, seg; i.ask, i.find, echo, lock, ...
> > i.oif/, r.in.wms/ are interesting as they contain platform
> > independent bash scripts.

Francesco P. Lovergine wrote:
> 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?)

do the debian (LSB, etc) regulations state that there can be no other
"etc/" besides the unix "etc/"?


More information about the grass-dev mailing list