On Sat, May 26, 2018 at 12:30:00PM +0100, Stuart Henderson wrote:
> : # $OpenBSD$
> :
> : COMMENT = GIS
>
> seems a bit short (I know, anyone who might use this already knows what GIS
> is, but it might be nice to explain more for other people). just writing
> out what the GRASS abbreviation means might help
>
> COMMENT = Geographic Resources Analysis Support System (GIS)
Yes of course, that was a WIP so far :)
> : CONFIGURE_ARGS = --with-gdal=/usr/local/bin/gdal-config \
> : --with-wxwidgets=/usr/local/bin/wx-config \
> : --with-geos=/usr/local/bin/geos-config \
>
> ${LOCALBASE}
Right :)
> : post-install:
> : # move docs to $PREFIX/share/docs/grass
> : #mv ${PREFIX}/grass/docs ${PREFIX}/share/doc/grass
>
> I know this type of software and understand why you want to keep their
> standard locations (and that's why I closed my eyes when I got to the
> grass-${GRASS_V}/lib/ bit in PLIST ;-) but maybe nice to symlink this
> into share/doc/grass?
Maybe a symlink yeah, but everything in grass points to its base
installation path, and the internal documentation browser/help system
expects to find its doc under it, etc.. so that would be useful only for
people wanting to look at the doc from outside grass gui or shell.
That's also why i didnt try installing the manpages in the regular dirs,
are there's way too many, and the names are too generic/might clash with
other things. A bit like the tcl manpages....
I met the freebsd grass maintainer at a conference some days ago and he
told me that he also kept the upstream layout for their port. The etc
subdir is also awkward, but it doesnt seem those are meant to be
admin/user-editable anyway.
Thanks for the feedback!
