or, how about a separate repo for all the parts of the developer
wiki relevant to building, testing, hacking, and a cron job that
records and pushes from the wiki files nightly?
Ideally Trac would use darcs as its backend, and I could run a local Trac
against a local darcs repository of the data, and then push my changes when
I'm online.
Unfortunately, Trac uses a database as its backend and custom revision
control for wiki pages, so we're out of luck. That is, unless those clever
Trac folks have changed things while I wasn't looking...
there seems to be some work on darcs+trac here:
http://progetti.arstecnica.it/trac+darcs/wiki/DarcsBackend
but i was thinking of a pedestrian approach, like
trac-admin <env> wiki dump <someplace>
with <someplace> being the wikidocs darcs repo, with a
suitable .darcs-boring file.
the cron job could dump the wiki once a week/night/whatever,
and then it is just record and push. it wouldn't give you a full
history, nor any change comments, so it wouldn't replace the
trac revision control. but it should make it possible to get the
essential parts of the wiki into the usual darcs-all pull stuff.
claus
_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc
