The first serious snow of the year is going on outside, and I’m wrapped up tightly in a wool blanket fixing 2 years worth of file and directory naming mistakes in Beagle.
Hooray, subversion is here!
We’ve taken a slightly different repo layout with Beagle than the standard one for other projects. To check out Beagle, run:
$ svn checkout svn+ssh://svn.gnome.org/svn/beagle/trunk/beagle
or, anonymously:
$ svn checkout http://svn.gnome.org/svn/beagle/trunk/beagle
The reason for this is that we’re keeping other code — right now just deprecated code that isn’t built — in our repo as well. At present we have attic and beagle, but the plan is to move libbeagle, the C API, out into its own module with its own releases to break a circular dependency with GTK.
We’ve never really used ChangeLog files in Beagle, based on the assumption that we’d be moving to Subversion a few years ago. Our plan is to generate the ChangeLog at make dist-time, in a manner similar to how Wouter describes it. The main downside to it is no offline ChangeLogs in between releases, but this has never been a real problem for me. You also will see GNOME usernames rather than real names, but I can finger if I need to. Now we just need to ensure that our commit messages are better than they have been with CVS.
One Trackback/Pingback
[...] It’s finally here! I made my first GNOME Subversion commit a few minutes ago, and am very much looking forward to finally giving the whole Banshee tree a much needed reorganization. I will be doing something similar to what Joe is doing with Beagle. There are a number of externally interesting and reusable components in Banshee that should be managed outside the main tree, but are still maintained by the project. [...]