[Pkg-privacy-commits] [libgsecuredelete] 48/168: Fill-in TODO list
Ulrike Uhlig
u-guest at moszumanska.debian.org
Thu Jul 7 20:06:38 UTC 2016
This is an automated email from the git hooks/post-receive script.
u-guest pushed a commit to branch master
in repository libgsecuredelete.
commit ea06ddfd387913c0a7dacf67d1678ffcdd9750de
Author: Colomban Wendling <ban at herbesfolles.org>
Date: Mon Feb 22 20:46:55 2010 +0100
Fill-in TODO list
---
TODO | 34 ++++++++++++++++++++++++++++++++--
1 file changed, 32 insertions(+), 2 deletions(-)
diff --git a/TODO b/TODO
index b9d16ca..5eca3a6 100644
--- a/TODO
+++ b/TODO
@@ -10,6 +10,33 @@ See result of `rgrep FIXME gsecuredelete` and `rgrep TODO gsecuredelete` too.
FIXMEs:
+* Fix progress behavior when deleting folder(s):
+ srm reports the progression for each files in the directory and not for the
+ directory itself. The problem is obviously that then the progress overflows
+ the percent (100*(n_files_in_dir -1)).
+ I see 3 "fixes" with pro and cons:
+ 1) Just don't report over 100% (clamp).
+ pros:
+ * Easy.
+ cons:
+ * The progression is obviously wrong, stuck to 100% after the first
+ file.
+ 2) Report (n % 1.0), so overflow are something like restarts.
+ pros:
+ * Should be quite easy;
+ * Better than 1).
+ cons:
+ * Not so exact, and can be quite discouraging to the user too.
+ 3) Count files in the directory.
+ pros:
+ * The progress is exact.
+ cons:
+ * This is resources-greedy;
+ * Perhaps a little overkill.
+
++ Better design for the arguments, allowing subclasses not to need to add
+ parent's supported arguments themselves.
+
+ Get the pass number reported by the program rather than guessing it.
(gsecuredelete/securedelete-operation.vala:88).
Not sure it is useful or really cleanly doable.
@@ -17,7 +44,7 @@ FIXMEs:
? (SwapOperation) is /proc/swaps a good method to know if a swap device is in
use?
Neither sure it is wrong to read /proc/swaps nor the swap wiping is supported
- in practice on non-Linus OS.
+ in practice on non-Linux OS.
TODOs:
@@ -25,10 +52,13 @@ TODOs:
This needs a courageous user! (Having a small amount of memory is probably
better as this operation may be slow (as the manual of smem says)).
++ Add a "message" argument to the progress callback with the (possibly empty)
+ progress message?
+
+ Be able to work as another user? (gsecuredelete/async-operation.vala:40)
find informations about this issue and what can/could/should be done to
fix it.
- Perhaps it is not the library that should provide the functionnality but
+ Perhaps it is not the library that should provide the functionality but
the caller program that may grant its rights or so, don't know.
- Support for canonical names/paths. (gsecuredelete/delete-operation.vala:66)
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-privacy/packages/libgsecuredelete.git
More information about the Pkg-privacy-commits
mailing list