Gerard Meijssen wrote:
Consequently, use it with care AND I do not think that
this should be a
recommended strategy for our average re-users of MediaWiki and its software.
Certainly not for average reusers. Also, blindly running it from cron
seems a bit risky.
The current practice is that all the extensions that
are
used will be given the same revision number. When you have one other
extension, you will not know what the effect is of running this script.
It assumes that the mediawiki folder is a checkout from mediawiki svn
and will update it to the specified revision. I don't see how it would
update to that revision folders of a different svn server.
Hoi,
This script assumes that you have the same software as is running on the
Wikimedia servers.
Also it is assumed that the underlying software is the
same as well (think
LAMP).
Which software could be different?
Every now and then the underlying software is patched
or new
application are installed to make the software work well.
Yes. Live hacks are a much bigger issue IMHO. They aren't even available
so reusers can't see what is the really running code (supposed they
tried to run trunk but found a patched bug!).
Given that this is
not handled by Werdna's software it is a scenario that is not without its
dangers.