From c5b052cbbda14c5c33127890d4a9842b8dee826a Mon Sep 17 00:00:00 2001 From: intrigeri Date: Mon, 2 Aug 2010 16:00:37 +0200 Subject: [PATCH] explored possible ways to do it, got trapped. --- doc/todo/po:_remove_po_files_when_disabling_plugin.mdwn | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/doc/todo/po:_remove_po_files_when_disabling_plugin.mdwn b/doc/todo/po:_remove_po_files_when_disabling_plugin.mdwn index 26b1964ba..0801f7fcd 100644 --- a/doc/todo/po:_remove_po_files_when_disabling_plugin.mdwn +++ b/doc/todo/po:_remove_po_files_when_disabling_plugin.mdwn @@ -2,3 +2,10 @@ 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]] -- 2.26.2