Re: [Pkg-grass-general] Re: Updated grass 5.7 package
On Thu, Dec 02, 2004 at 05:20:42PM -0500, Steve Halasz wrote:
> On Wed, 2004-12-01 at 01:15, Dan Jacobson wrote:
...
> > Also mention to use g.list type=oldvect or else the user will think
> > they have been hacked.
... or they read the instructions:
g.list help 2>&1 | grep vect
options: rast,rast3d,oldvect,vect,asciivect,icon,labels,sites,
oldvect (old (GRASS 5.0) binary vector files)
vect (binary vector files)
asciivect (ascii vector files)
> >
> > And mention if one doesn't use g.setproj what bad will happen.
... or they read the manual page of g.setproj.
AFAIK there is also a warning/query issued once the user start it.
Usually a user does not have to use it (without reading the instructions).
If a user makes a mistake, when defining the projection etc,
s/he can simply re-run it to define it again. Data are not touched
at all by this module.
> I intend to include a note about upgrade issues somewhere. As a debconf
> screen or administrator email. I haven't gone through an upgrade myself,
> so I don't know exactly what the issues are. I have seen some conversion
> info here:
> http://grass.itc.it/grass57/tutorial/ex_basic.html#convert
Here is even more (growing):
http://grass.gdf-hannover.de/twiki/bin/view/GRASS/GrassSixTutorial
-> Getting started - how to migrate to the new GRASS version
> > I see the two libgrass's still are called libgrass5.7.
>
> This is on purpose. I'm not sure how stable the grass API is. But the
> libgrass packages probably need to be versioned to prevent dependant
> packages from breaking when grass is upgraded. I'm not wise in the ways
> of library packaging. But I'm going on the information here:
> http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html
>
> grass libraries don't have sonames so what the proper package names
> should be will require some further investigation.
Maybe forth to fix that in our CVS?
Markus
Reply to: