[dokuwiki] Re: how to use developer version of dokuwiki

Oliver Geisen wrote:

Hello,
i've read about darcs and some docs about how to get dokuwiki developer version. Fetched dokuwiki from repository using "darcs get ..." and understand how to get current patchlevel using "darcs pull". 

But some thinks are not quite clear for me:
- install.php will not work because of missing hash (okay, i can add it myself, but is it the way to do it? or should "developers" never use install.php ;-)) - if i change the repo-clone e.g. by adding templates, etc. does this has any effect on getting further patches ? - what happens to local changes in a sourcefile if that file gets patches inside repository? Are my changes lost (i think so). Or - should i keep a local, unmodified copy of the darcs pull and "clone" my dokuwiki instances from it, or can i savely use the pull directly ?
My intention was to stay up to date with dokuwiki changes and make little modifications by myself. As far as i understand darcs, this should be possible, even i don't really know how yet :-) 
I've read about an internal patch-Plugin, would this suite better ?

Oliver Geisen

--DokuWiki mailing list - more info at
http://wiki.splitbrain.org/wiki:mailinglist


Read up some more in the darcs wiki.

Darcs keeps a pristine copy.  You don't need to.
Basically, if a pulled patch clobbers the same piece of code you have changed you will get a problem. If it doesn't you won't. Darcs is a proper version control system - so the problem you will get is minor, darcs will notify you of it and its easy to rectify.
The whole point of having a default and local configuration files, specific plugin and template folders is to allow customisation. Its probably also true that the people who use darcs and contribute to the development are among the most active customisers of DW. We'd look pretty silly if every time we updated we had hours worth of work to put back those customisations. ;) 



Cheers,

Chris
--
DokuWiki mailing list - more info at
http://wiki.splitbrain.org/wiki:mailinglist

Other related posts: