[Box Backup-dev] DocProject editing setup

[Martin Ebourne]

On Fri, 2006-08-11 at 00:50 -0700, E.W. Peter Jalajas wrote:
> 1) Here's what I have for xml editors:  

Of course, XML is just a text file. You can use absolutely any editor to
edit XML so if you're proficient with vim then that would be perfectly
ok. The only advantage of a real xml editor is that it should make it
easier for you by automating some of the tag entry etc. If you're just
making small changes it's easier to use your favourite editor. If you're
doing a lot of xml work it's worth learning a new tool.

> 2) Here's what I have for xsltproc and docbook:
> How does that look?  1.68 looks bad per the DocProject page.  I'm not
> sure I want to start messing with a dependency hell, but I'm open to
> suggestions.  Maybe I can just stay away from man pages? 

I've not tried it but Per just reports excessive whitespace in man
pages. From a point of view of just contributing to the docs I doubt
that's really an issue.

> 4) Here's what I have for subversion:
> The boxbackup-dev mailing list mentions transferring the svn repository
> and integrating with trac.  Do I need to do anything with that info?

Ok, you're sorted with svn now. No, there's nothing you need to do
different now the trac move has completed.

Just execute:

svn co http://bbdev.fluffy.co.uk/svn/box/trunk boxbackup

Then edit away. Use:
   svn st
or
   svn diff
to keep track of your changes.

You won't be able to commit since the svn committer accounts are
different to the trac ones. But that's not an issue. Simply svn diff
from the top of the working copy and attach the result to an email or a
new ticket in trac.
 
Cheers,

Martin.