If you take code from the repository that is not a version tagged as a
release, you are downloading ongoing development work. There is no guarantee
that what is currently checked in will work in anyway whatsoever!
Well, everywhere I worked people always apoligized when they committed something that broke the build. A broken build should be an exception.
A LOT of people are running into this problem with the James HEAD. Most people just want to play around with the source, to get some grip on the matter. James has a rather complicated architecture, so people try to stab at it from various angles to get to know it. The most obvious thing to do is to download the source package, but the next best thing to try is CVS. And if the HEAD doesn't compile, it is not uncommon to ask what's going on...
It bothers me a little bit that that some of the main developers take more effort in complaining about bewildered users than taking some rather simple measures that would really prevent a lot of questions on this list.
I would suggest to
1) Make the HEAD compile. Artur Wronski has recently posted some patches to accomplish this.
2) Put a simple README_THIS_IS_PROBABLY_NOT_THE_VERSION_YOU_WANT_TO_PLAY_WITH.txt in the HEAD pointing to the current active branch.
Thank you
Hes.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
