[dokuwiki] Re: Best practices of multiple documentation releases
- From: "Bob McConnell" <rvm@xxxxxxxxx>
- To: <dokuwiki@xxxxxxxxxxxxx>
- Date: Tue, 3 Jul 2007 10:59:26 -0400
> From: YC Chan
> Sent: Tuesday, July 03, 2007 10:36 AM
> To: dokuwiki@xxxxxxxxxxxxx
> Subject: [dokuwiki] Re: Best practices of multiple documentation
releases
>
> Sorry, I have no background in PVCS, Perforce etc. I can't discuss
> their functionality. I guess that they are capable of following
multiple
> threads, which Chris suggested dropping out earlier in the thread.
>
> Is there a Open Source RCS that can be integrated into DokuWiki ?
> Or how much of a development effort does a 'decent' RCS takes ?
> (And any volunteers?)
>
> IMHO, no Wiki is expected to be a full fledged Code Version Control
> System. Its intended users are simple people who wouldn't compare it
> with Perforce, etc.
Exactly, which is why you should export the release snapshots to a real
RCS.
There is DARCS, which is used for Dokuwiki code. There is also git,
which was recently written by Linux Torvalds to store the Linux kernel
code. IIRC it took him about four months. I believe there are a couple
of older packages distributed with many Linux systems. CVS sticks in my
mind, as does RCS which is a GNU package. Both of these are rather old.
You can get more ideas at
<http://en.wikipedia.org/wiki/Revision_control>.
Perforce and PVCS are commercial programs, although Perforce does offer
stripped down packages free for personal use.
Is my memory completely gone, or was someone talking earlier about using
DARCS as a back end for Dokuwiki?
Bob McConnell
--
DokuWiki mailing list - more info at
http://wiki.splitbrain.org/wiki:mailinglist
Other related posts:
