<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7226.0">
<TITLE>[pmwiki-users] Re: How to 'automatically' keep a deployed PmWiki install up to date?</TITLE>
</HEAD>
<BODY>
<DIV id=idOWAReplyText90140 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>To date we've been looking at
source code configuration systems to help us maintain our system
installations. This approach effectively remembers what you have checked
out allowing you to 'update' your installations.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>What about the reverse perspective, how can
get we request from the PmWiki core a list of all installed plug-ins - perhaps a
plug-in registration mechanism?</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>A single Wiki page could be configured to
report the system configuration.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Any ideas on how this can be achieved over
and above {$Version} for PmWiki core?</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2>-Steve.<BR></DIV></FONT></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> pmwiki-users-bounces@pmichaud.com on
behalf of chr@home.se<BR><B>Sent:</B> Sun 25/09/2005 17:49<BR><B>To:</B>
pmwiki-users@pmichaud.com<BR><B>Subject:</B> [pmwiki-users] Re: How to
'automatically' keep a deployed PmWiki install up to date?<BR></FONT><BR></DIV>
<DIV>
<P><FONT size=2>On Mon, 26 Sep 2005, Robin wrote:<BR><BR>> On Monday 26
September 2005 03:17, Crisp, Steve [UK] wrote:<BR>> > I still think a
separate repository, let's call it a staging area might<BR>> > simplify
things especially if the update mechanism needed nothing more<BR>> > than
you already have to run PmWiki (php, web server, browser). Unless<BR>>
> there is a php CVS client class out there that can be
reused!<BR>><BR>> Might I recommend that if you do something like this,
you look into<BR>> subversion. It's usable just the same as CVS (it was
designed to be easy<BR>> to go from one to the other), but avoids many of the
issues that you end<BR>> up unconsciously working around in CVS, leading to
less repository<BR>> maintenance and more just using it.<BR><BR>I agree... in
fact, maybe Patrick should switch pmwiki to subversion as<BR>well? That's
totally up to him of course, and pmwiki is so stable now that<BR>many of the
reasons for using subversion probably doesn't apply in case.<BR>But it might be
useful?<BR><BR>/Christian<BR><BR>--<BR>Christian Ridderström, +46-8-768 39
44
<A
href="http://www.md.kth.se/~chr">http://www.md.kth.se/~chr</A><BR><BR><BR><BR>_______________________________________________<BR>pmwiki-users
mailing list<BR>pmwiki-users@pmichaud.com<BR><A
href="http://host.pmichaud.com/mailman/listinfo/pmwiki-users">http://host.pmichaud.com/mailman/listinfo/pmwiki-users</A><BR></FONT></P></DIV>
</BODY>
</HTML>