496874ab27
Involved dropping some checks for .svn which didn't add anything, since if svn is enabled and you point it at a non-svn checkout, you get both pieces. The tricky part is add and rename, in both cases the new file can be in some subdirectory that is not added to svn. For add, turns out svn has a --parents that will deal with this by adding the intermediate directories to svn as well. For rename though, --parents fails if the directories exist but are not yet in svn -- which is exactly the case, since ikiwiki makes them by calling prep_writefile. So instead, svn add the parent directory, recursively. tldr; svn made a reasonable change in dropping the .svn directories from everywhere, but the semantics of other svn commands, particularly their pickiness about whether parent directories are in svn or not, means that without the easy crutch of checking for those .svn directories, code has to tiptoe around svn to avoid pissing it off. |
||
|---|---|---|
| .. | ||
| .gitignore | ||
| NEWS | ||
| README.Debian | ||
| changelog | ||
| compat | ||
| control | ||
| copyright | ||
| docs | ||
| link | ||
| postinst | ||
| preinst | ||
| rules | ||
README.Debian
It's a good idea, and in some cases a requirement, to rebuild your wikis when upgrading to a new version of ikiwiki. If you have a lot of different wikis on a system, this can be a pain to do by hand, and it's a good idea to automate it anyway. This Debian package of ikiwiki supports rebuilding wikis on upgrade. It will run ikiwiki-mass-rebuild if necessary when upgraded. The file /etc/ikiwiki/wikilist lists the setup files of wikis to rebuild, as well as the user who owns the wiki. Edit this file and add any wikis you set up. You can also allow users to maintain their own list of wikis to rebuild, by listing their usernames in /etc/ikiwiki/wikilist without corresponding setup files. ikiwiki will then read their lists of wikis from .ikiwiki/wikilist in their home directories. The examples directory contains the source to some example wiki setups.