6.0.0 beta2 was released, you can get the source package:
http://grass.itc.it/grass60/source/grass-6.0.0beta2.tar.gz
or you can download it from cvs:
cvs -z3 co -r grass_6_0_0_beta_2 grass51
This is probably the last 6.0.0 beta.
Radim
Radim Blazek said:
6.0.0 beta2 was released, you can get the source package:
http://grass.itc.it/grass60/source/grass-6.0.0beta2.tar.gz
or you can download it from cvs:
cvs -z3 co -r grass_6_0_0_beta_2 grass51
This is probably the last 6.0.0 beta.
yay! 
Congratulations to everybody who's been making this happen!
-- Mark
Mark P. Line
Polymathix
San Antonio, TX
Radim Blazek wrote:
or you can download it from cvs:
cvs -z3 co -r grass_6_0_0_beta_2 grass51
1). Does this imply that 6.0b2 requires the 5.1 codebase?
2). Has the merge to 6.0 that's been talked about happened yet? (Last
note on the subject from Hamish - (02-03-05) - says "maybe we should
wait until after 6.0.0beta2 is tagged and tarballed).
3). If not, when?
4). If I have the 5.1 codebase (6.0b1) from a week and a half ago, what
is the best way to get just an update?
4.1). or should I grab the whole thing again?
Currently I'm not contributing back, just trying to build the latest.
Sorry, its just that the versioning is getting a little confusing.
Best regards,
Jack Varga
On Feb 7, 2005, at 9:29 PM, Jack Varga wrote:
Radim Blazek wrote:
or you can download it from cvs:
cvs -z3 co -r grass_6_0_0_beta_2 grass51
1). Does this imply that 6.0b2 requires the 5.1 codebase?
2). Has the merge to 6.0 that's been talked about happened yet? (Last
note on the subject from Hamish - (02-03-05) - says "maybe we should
wait until after 6.0.0beta2 is tagged and tarballed).3). If not, when?
4). If I have the 5.1 codebase (6.0b1) from a week and a half ago, what
is the best way to get just an update?4.1). or should I grab the whole thing again?
Currently I'm not contributing back, just trying to build the latest.
Sorry, its just that the versioning is getting a little confusing.
Best regards,
Jack Varga
I just did this today and also find the version numbering to be getting rather obtuse. I had not cvs updated since very early in the life of beta1, so I decided to stat over. Correct me if I got this wrong, but my attempt to get the latest was to:
cvs -z3 checkout grass51
then cvs update -dP in the new grass51 directory.
My assumption was that would be the daily build.
Kirk R. Wythers
Dept. of Forest Resources
University of Minnesota
email: kwythers@umn.edu
tel: 612.625.2261
fax: 612.625.5212
Radim Blazek wrote:
> or you can download it from cvs:
>
> cvs -z3 co -r grass_6_0_0_beta_2 grass511). Does this imply that 6.0b2 requires the 5.1 codebase?
No. The code base merge detailed on the "timeline" web page happened
November 9 2004.
If it is easier, just grab the .tar.gz from:
http://grass.ibiblio.org/grass60/source/grass-6.0.0beta2.tar.gz
(or a local mirror)
2). Has the merge to 6.0 that's been talked about happened yet? (Last
note on the subject from Hamish - (02-03-05) - says "maybe we should
wait until after 6.0.0beta2 is tagged and tarballed).
No, that was refering to renaming the internal directory structure of
the cvs so the checkout command would be "cvs co grass6" not
"cvs co grass51".. this is to make the versioning less confusing.
(grass 5.1 IS grass 5.7 which 6.0 is pulled from)
4). If I have the 5.1 codebase (6.0b1) from a week and a half ago,
what is the best way to get just an update?
generally:
cd /to/where/grass/source/is
cvs -z3 update -dP
gets you the latest version of everything.
I put a file called .cvsrc in my home directory containing the
following instructions:
-z3
diff -u
update -dP
Then just "cvs update" works correctly.
4.1). or should I grab the whole thing again?
generally cvs update is less to download, but for testing a new release
downloading the source distribution whole certainly has its merits -
recreating the exact experience most users will face.
Sorry, its just that the versioning is getting a little confusing.
We are working our way out of that. The "grass51" cvs directory is
pretty much the only non-logical (on some level) bit left I think, and
that will be taken care of in the near future hopefully.
regards,
Hamish
On Tue, Feb 08, 2005 at 06:16:06PM +1300, Hamish wrote:
> Sorry, its just that the versioning is getting a little confusing.
We are working our way out of that. The "grass51" cvs directory is
pretty much the only non-logical (on some level) bit left I think, and
that will be taken care of in the near future hopefully.
The CVS module is now called "grass6",
see my other email for details.