MOL release candidate available

[Gavin Hemphill]

Samuel:
	I've been following the progress of MOL fairly closely and trying to 
test the changes as you progress (make that changesets since I'm using 
the BK repo).  One of the things I tend to do is build the rpm's since I 
actually use MOL on a daily basis and I find it much easier to back up 
to my previous stable position using rpm rather than trying to track 
down all the pieces by hand.
	There appear to be a couple of things that make this more difficult 
than it should be when using BK.  The first thing is that you only tag 
the actual releases (and I think the actual 0.9.66 is at least one 
changeset later than the tag would indicate but I'm probably wrong 
there).  Bk revtool lets me look at the changesets but the comments 
don't usually contain any indication of things like if it's a release 
candidate.  I guess the real plea here is for more tags since the actual 
version number of MOL doesn't increase incrementally (and I can see why 
that would be a pain given the complexity of the build structure.
	The other problem I usually have is that the rpmbuild process tends to 
be the last thing fixed which makes it more timeconsuming to test things 
as they move along.  For example, the release candidate seems to be 
trying to use rpm rather than rpmbuild, and a quick check of the code 
shows that if rpmbuild is in the path it should wind up being used).  I 
haven't had time to track this down yet.
	The regular make compiles fine under a fully patched YDL 3.0.1 system 
with 2.4.22-2g and if I get some time this evening I'll try it out :-)
	G++