https://bugzilla.wikimedia.org/show_bug.cgi?id=18242
--- Comment #8 from Aryeh Gregor <[email protected]> 2009-04-02 15:03:09 UTC --- Without explicit Subversion support, we could probably do this by calling "svnversion" a few dozen times for every Special:Version view. But that only works for actual Subversion checkouts, not tarballs based off Subversion checkouts. We could include the .svn directory in the nightly extension tarballs, perhaps . . . then it would work as long as svn is installed (which it won't be on most shared hosting, if the software can even use exec() to begin with). Another way to do this would be to use an on-commit hook of some kind. Or we could add the functionality to ExtensionDistributor, which would at least solve a fairly common case (this could be used in addition to allowing svnversion to be called for those who do a direct checkout). (In reply to comment #7) > I've closed Subversion issue 3389 as INVALID. Please see the following FAQ to > see why, and with a possible workaround: > http://subversion.tigris.org/faq.html#version-value-in-source I don't think it would be impossible for Subversion to do this efficiently. You'd "just" need to maintain an index of all files with the marker in them, checking each file for it whenever a change to it is committed. Then whenever the revision number is incremented, all files in the index are updated, and you don't have to scan all files in the repo. That might be way too much effort for such a minor feature, of course. -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
