How do I get the current stable version from CVS?
Moderator: Moderators
How do I get the current stable version from CVS?
cvs co seems to give me unstable code (0.307) which raises an exception almost every time a file completes downloading.
How can I get the stable code from cvs? Tags haven't been applied for a long time, seemingly...
Rob
How can I get the stable code from cvs? Tags haven't been applied for a long time, seemingly...
Rob
That's all well and good, but I have a few local patches that I'd like to apply to the latest stable version. cvs does this automatically - having to reapply the patches manually is a pain.
Not using tags seems a bit strange in a cvs repository with frequent releases. Is there a date I could safely use instead?
Not using tags seems a bit strange in a cvs repository with frequent releases. Is there a date I could safely use instead?
-
- Forum Moderator
- Posts: 1420
- Joined: 2003-04-22 14:37
According to the project page, 0.306 was released on 9th of January, so I guess you should be going for something around that date.ugumba wrote:Not using tags seems a bit strange in a cvs repository with frequent releases. Is there a date I could safely use instead?
As an aside, it's nice see that the public CVS is now in sync with the developer view.
-
- Posts: 506
- Joined: 2003-01-03 07:33
A short comment, its more often that the release is shipped without beeing in sync with CVS. Usualy some changes will come in after.. like the version.h file et.c. And if you need stable versions, then use the tar-balls located at SF. CVS has its advantages as you say.. but you can always use diff towards the tar-balls and merge either with a "editor" that easily handles diff-files (yes this requires work.. but then again.. cvs will also sometimes)..
Everyone is supposed to download from the hubs, - I don´t know why, but I never do anymore.
Thanks for your comments guys.
After checking the cvs diffs using '-D "January xx"', I figured the repository was quiet for a few days after the 10th, and used 'cvs update' to backtrack my locally patched copy to that date. Worked great!
Gotta love cvs, though this would have been much easier with a simple tag from the developers.
Now, I'm looking forward to the hashing features I caught a glimpse of!
After checking the cvs diffs using '-D "January xx"', I figured the repository was quiet for a few days after the 10th, and used 'cvs update' to backtrack my locally patched copy to that date. Worked great!
Gotta love cvs, though this would have been much easier with a simple tag from the developers.
Now, I'm looking forward to the hashing features I caught a glimpse of!
-
- Posts: 506
- Joined: 2003-01-03 07:33
-
- DC++ Contributor
- Posts: 3212
- Joined: 2003-01-07 21:46
- Location: .pa.us
Only one person ever commits to CVS, though more may have access.ugumba wrote:Gotta love cvs, though this would have been much easier with a simple tag from the developers.
Also, if your patches are of general interest, contributions are always welcome.
CVS is nice, I don't think the releases are tagged, or CVS itself is used to its potential. Personally, I like subversion just a bit more - it makes pulling a given release a bit easier than remembering release dates.