summaryrefslogtreecommitdiff
path: root/doc/todo/po:_remove_po_files_when_disabling_plugin.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'doc/todo/po:_remove_po_files_when_disabling_plugin.mdwn')
-rw-r--r--doc/todo/po:_remove_po_files_when_disabling_plugin.mdwn11
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/todo/po:_remove_po_files_when_disabling_plugin.mdwn b/doc/todo/po:_remove_po_files_when_disabling_plugin.mdwn
new file mode 100644
index 000000000..0801f7fcd
--- /dev/null
+++ b/doc/todo/po:_remove_po_files_when_disabling_plugin.mdwn
@@ -0,0 +1,11 @@
+ikiwiki now has a `disable` hook. Should the po plugin remove the po
+files from the source repository when it has been disabled?
+
+> pot files, possibly, but the po files contain work, so no. --[[Joey]]
+
+>> I tried to implement this in my `po-disable` branch, but AFAIK, the
+>> current rcs plugins interface provides no way to tell whether a
+>> given file (e.g. a POT file in my case) is under version control;
+>> in most cases, it is not, thanks to .gitignore or similar, but we
+>> can't be sure. So I just can't decide it is needed to call
+>> `rcs_remove` rather than a good old `unlink`. --[[intrigeri]]