On Tue, Nov 30, 2010 at 4:12 AM, Glynn Clements <[email protected]> wrote: > Francesco P. Lovergine wrote: > >> Something like: >> >> make build-core | build-xdriver | build-wxgui | build-tkgui >> >> make install-core | install-xdriver | install-wxgui | install-tkgui >> >> would be more modular and clean. Of course, one can always now >> install the whole beast, use only what is of interest and avoid >> installing all dependencies. As said, it works too. >> But I - as packager - would prefer avoiding tons of silly reports >> about 'command X is not working because Y is missing' and installing >> most required dependencies for all commands provided. > > You can package it how you want, but I don't think that it's realistic > to structure GRASS around individual packagers' policies (e.g. who > says what is "core" and what isn't).
Well, I think that Francesco suggestion above is pretty clear. It does not look like too strange to me and sufficiently generic. Markus _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
