darcs - DokuWiki User Forum

3AtÜ

2008-03-12, 01:43 #1

Member since Mar 2007 · 29 posts
Group memberships: Members

Show profile ·

Link to this post

Subject: darcs

Hi,
since I'm tired of messing up my installations with a lot of devel code, I tried out darcs. After reading the manual (not in detail, yet) and the darcs-related wiki page, I have still one important question not answered:

What is the best way to develop and test? I mean: I have pulled the current devel code and applied all patches. Now I want to extend this code with a superb feature. But for that I need dokuwiki to run. That means: I have to rename and edit some config-files and dokuwiki will create some files in the data dir. Darcs will notice those changes of course, but they don't interest me. I want darcs rather to observe only the files relevant for my feature.

I thought of creating a second repository, make all initially changes (local.php, acl.auth.php....) and record them as patch. I would then edit source code only in my first repository, create a patch and copy that to my second "test repo". But this is far away from usable and wouldn't work neither.

Something that I get completly wrong?

Thank You in Advance

3AtÜ

2008-03-12, 08:40 #2

Member since Mar 2007 · 29 posts
Group memberships: Members

Show profile ·

Link to this post

Hhm, another way could be, to leave the repository as it is and create a copy of it. The copy will be my working test system, which I install and configure.
Now I have to options:
* edit the code in the repository and mirror the changed files to the working test system everytime I want to test it (keeps the repository clean)
* edit the code in the working copy, test it there and move the changed files to the repository, when I have finished editing and testing

Well, I would chose the second way. But I'm not sure, if this is the right way. Especially when I have edited many files, I could loose the orientation...

chi (Moderator) 2008-03-12, 11:11 #3

Member since Jun 2006 · 607 posts · Location: Munich Germany
Group memberships: Global Moderators, Members

Show profile ·

Link to this post

In reply to post #1

Quote by 3AtÜ:
Something that I get completly wrong?

Kind of

. If you do the first checkout of the devel repository, the acl.auth.php, local.php and users.auth.php aren't there. You have to either run the installer (best option) or create them yourself. And here comes the important part. Newly added files aren't tracked by darcs unless you tell it so with a:

darcs add users.auth.php

That means, as long as you don't do darcs add <file> you don't have to worry about files below data/* or your configuration settings being added to the repository. In order to reduce the "risc" of messing with the data directory you could configure DokuWiki to use a data directory which is outside of the repository (that's what I do).

In terms of generall workflow there are different opinions. I work on one copy of the repository without problems. Others prefer to check out a master repo and then work on a local copy of this and push/pull from there (like your second approach). I might make sense if you happen to work on different things at the same time, but IMHO it has nothing to do with keeping the repository clean.

However, it's always a good idea to inspect patches before sending them, to avoid stuff like left over debugging code and the like.

HTH

Please add [SOLVED] to the initial thread subject if you feel your question has been answered.

3AtÜ

2008-03-12, 21:07 #4

Member since Mar 2007 · 29 posts
Group memberships: Members

Show profile ·

Link to this post

ah, got the point, thank you very much.