Jamie, Lots of good points. The reason I am building in a different directory is just to keep the build clutter away from the source code. The main things in my next commit will be lou_debug and the changing of some names in the code, but these affect almost everything else I'll be committing. I will definitely keep future commits down to single issues if possible. John On Sat, Jan 10, 2009 at 02:40:33PM +1000, James Teh wrote: > Hi John, > > As you suggest, it is recommended to do your development in your working > copy; i.e. your checkout of svn. Aside from the obvious ease of use, > this means you can also use commands like: > svn status: to find out what files you have changed, added, removed, etc. > svn diff: to get a diff between the current revision of svn and your > working copy, which is very useful if you want to know what you are > about to commit > svn revert: if you want to revert some changes you have made in your > working copy; i.e. revert files to the current svn revision > Of course, you can use these commands on individual files and > directories. (In fact, svn revert won't work on the whole tree by default.) > > I don't quite follow why you want to build in a different directory; you > can quite safely build in your working copy, as the generated files will > be ignored by svn. You can use make distclean to clean the tree > completely. If you do have some good reason for building in a different > directory, there's of course nothing wrong with that. > > Due to the fact that you have quite a few uncommitted changes, this > commit will probably include a lot of unrelated changes. However, in > future, I'd recommend that you try to commit unrelated changes > separately. This makes it much easier to work out why something was > changed when examining logs, reading annotations, etc. It also makes it > much simpler to revert a given change if it was later found to be > undesirable. If you commit many unrelated changes in the same commit, > this becomes very difficult. > > When you commit, be sure to include a detailed log message with your > commit detailing what has changed. > > If you are working on several unrelated changes in the same file, but > some of those changes may not be finished for a while, you may wish to > create a branch. This is a separate line of development which you can > then merge into the main code (trunk). This is somewhat more complex and > requires an understanding of such concepts, so you may want to wait > until you are more familiar with svn before tackling this. > > Hope this helps. > > On 10/01/2009 2:02 PM, John J. Boyer wrote: > >I have a live copy of the svn repository. So far I've been doing > >development and testing in a separate directory tree. However, this > >means that I will have to copy all changed files from that tree to the > >svn tree before making a commit. This can lead to errors. It seems to me > >that I could do development directly in my copy of the repository. If I > >run autogen.sh in that copy the generated configure Makefile.in, etc. > >files should make no difference to svn, since they aren't in its file > >lists. I can then do building in a separate directory with a statement > >like ../svnrep/configure, make, make install. Then when testing is done > >I can just do a commit without having to worry about not having copied > >some files. > > > >I'm planning a big commit early next week. The problem with French Grade > >2 braille has been fixed. There will also be a completed lou_debug tool. > >een replaced by "TranslationTable." > >You will notice that in the code > >"ContractionTable" has been replaced by "TranslationTable." The former > >term was a holdover from brltty, but it doesn't make much sense in > >documentation, considering the expanded role of the table. The change is > >actually long overdue. > > > >Thanks to all of you who are helping me learn what I need to know to > >make this project a real success. > > > >John > > > > -- > James Teh > Email/MSN Messenger/Jabber: jamie@xxxxxxxxxxx > Web site: http://www.jantrid.net/ > For a description of the software and to download it go to > http://www.jjb-software.com -- My websites: http://www.godtouches.org http://www.jjb-software.com Location: Madison, WI, USA For a description of the software and to download it go to http://www.jjb-software.com