[GRASS5] Proposal for a new GRASS directory structure
Bernhard Reiter
bernhard at intevation.de
Tue Sep 12 05:41:36 EDT 2000
On Mon, Sep 11, 2000 at 04:19:31PM -0400, Eric Mitchell wrote:
> First, is there is a list of what needs to be done before GRASS-5.0
> is considered final? A list of remaining modules to get working?
Markus hat something similiar to this in mind I think.
> A list of known bugs that needs to be whittled down? If there isn't
> a solid target to aim for, we'll never hit it.
We should come up with them then.
> As far as reorganizing the source, how would it make sense to split
> up GRASS? What set of modules would provide a reasonable breakdown
> of the whole GRASS distribution? grass-base, nviz, nonGPL, etc? I'd
> recommend reorganizing with that layout in mind.
We cannot distribute nonGPL stuff with GRASS. Nobody can use it.
Yes, grass-base and then thematic packages would be nice.
nviz is 3D and even has other requirements (OpenGL/Mesa).
> My recommendation
> for dealing with the reorganization in the CVS repo, is to declare
> the current tree dead, and reimport the source in the reorganized
> layout somewhere new in the repository. You can still get the old
> information if necessary, but moving files around a cvs repository
> tends to be a pain.
This might work. But this is also the time to do a more radical
cleanup and we can only do that on the development tree.
Even major source code reorganisation should IMO not done in a beta
phase of a project.
Bernhard
--
Professional Service around Free Software (intevation.net)
The FreeGIS Project (freegis.org)
Association for a Free Informational Infrastructure (ffii.org)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 236 bytes
Desc: not available
Url : http://lists.osgeo.org/pipermail/grass-dev/attachments/20000912/c82ba3eb/attachment.bin
More information about the grass-dev
mailing list