| View previous topic :: View next topic |
| Author |
Message |
ned14
G
Joined: 13 May 2007
Posts: 65
Location: St. Andrews University, Scotland
|
 Posted: Wed Oct 31, 2007 12:52 am Post subject: Attention: Brook shall move to SVN repository this week |
 |
|
Dear All,
Mike has given me permission and admin privs on sourceforge to migrate Brook from CVS to Subversion. This will happen during this week after I have experimented sufficiently with the migration process (it's my first).
After I start, CVS will be locked down and no further writes permitted (though reads will still be allowed). After the SVN migration is finished, I will open a new branch and commit my Brook FBO, GLSL, multi-GPU, SSE and OpenMP upgrade to an experimental branch (see http://www.gpgpu.org/forums/viewtopic.php?t=4647&postdays=0&postorder=asc&start=15) in SVN. The CVS repository will then be permanently retired from service.
I hope this doesn't inconvenience anyone. Sorry I can't give a fixed date as I have final year coursework to do! Please do feel free to comment here if you wish.
Cheers,
Niall |
|
| Back to top |
|
 |
deep_5z
.
Joined: 01 Oct 2007
Posts: 12
|
| Posted: Wed Oct 31, 2007 4:16 pm Post subject: |
|
|
| I already installed brook through CVS. Now do I need to again reinstall using the new SVN??? |
|
| Back to top |
|
|
ned14
G
Joined: 13 May 2007
Posts: 65
Location: St. Andrews University, Scotland
|
| Posted: Thu Nov 01, 2007 7:45 pm Post subject: |
|
|
| deep_5z wrote: | | I already installed brook through CVS. Now do I need to again reinstall using the new SVN??? |
If you wish to make use of any new features added to Brook from this week onwards, then yes you will need to recheckout a fresh copy from SVN after the migration. If your current copy suits your needs, no need to upgrade.
The migration won't happen tonight at least - got a lab and a whole book by Milton Friedman to summarise into two hundred words due for tomorrow. Painful 
Cheers,
Niall |
|
| Back to top |
|
|
dom
GPGPU
Joined: 15 Nov 2004
Posts: 1478
Location: TU Dortmund, Germany
|
| Posted: Thu Nov 01, 2007 11:39 pm Post subject: |
|
|
I think the migration will work smoothly for all developers if you
(1) commit a README / MIGRATIONGUIDE to the old CVS (if I were you, I would also change the old Makefiles to display a warning instead of compiling (and compiling only with some special new target), but I'm paranoid by definition). My point is that not all users of brookgpu read these forums and your announcement.
(2) change the SF.NET pages to point to instructions on how to get the sources from SVN instead of CVS.
(3) eventually provide a new tarball release while you're at it.
(4) talk to Mark to have this put up on the main page, a new brookgpu release is always worth a new NEWS item 
just my 2px.
dom |
|
| Back to top |
|
|
ned14
G
Joined: 13 May 2007
Posts: 65
Location: St. Andrews University, Scotland
|
| Posted: Sun Nov 04, 2007 5:03 am Post subject: CVS to SVN migration complete! |
|
|
| dom wrote: | I think the migration will work smoothly for all developers if you
(1) commit a README / MIGRATIONGUIDE to the old CVS (if I were you, I would also change the old Makefiles to display a warning instead of compiling (and compiling only with some special new target), but I'm paranoid by definition). My point is that not all users of brookgpu read these forums and your announcement. |
I added a file called 'bin' to CVS which should prevent successful builds and/or CVS updates from now on. I also added a file pointing out that CVS is closed in favour of SVN
| dom wrote: | | (2) change the SF.NET pages to point to instructions on how to get the sources from SVN instead of CVS. |
Done!
| dom wrote: | (3) eventually provide a new tarball release while you're at it.
(4) talk to Mark to have this put up on the main page, a new brookgpu release is always worth a new NEWS item |
Shall do as soon as "Niall's Update" branch is anywhere near ready for release.
You can all find the shiny new SVN repository at http://brook.svn.sourceforge.net/viewvc/brook/. Instructions for usage are at https://sourceforge.net/svn/?group_id=96847 or more verbosely at https://sourceforge.net/docs/E09.
Just for all your information, I have made use of some advanced SVN features in the migration:
1. Quite a few of the Brook source files had inconsistent CR/LF endings. This broke GNU make and even caused a GCC parsing bug which took me ages to nail. Subversion always checks out to machine native format and it also insists that input is CR/LF consistent. This problem will never again emerge when using Subversion.
2. Subversion is fully aware of binary files and their MIME type unlike CVS. I have demarcated them appropriately.
3. I've converted the .cvsignore files into SVN metadata which perform the same action.
4. I have moved all the tags & branches from CVS into 'temp' directories and moved the release tags into their own directory. I felt this was much cleaner. Subversion correctly handles renames unlike CVS.
Almost all of the CVS history has been maintained, though I pruned off any references to CVSROOT which have castrated some of the tags which tagged too much.
If any of you find any problems with this migration, please let me know as soon as possible so I can fix it before the commits mount up.
Cheers,
Niall |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
