libgsecuredelete0 0.1-2 / usr / share / doc / libgsecuredelete0 / TODO

'*' means important things, '+' means cool things, '-' means things that might
be done.
FIXMEs are things that needs to be fixed (the code is here but needs fixing);
TODOs are things that needs to be created (there is no code for them):
There are some FIMXE/TODO in the code that are not listed here: it could be
either a mess or a code-specific thing that is not important enough or too
specific to be listed here.

See result of `rgrep FIXME gsecuredelete` and `rgrep TODO gsecuredelete` too.


FIXMEs:
+ 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.

? (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-Linux OS.


TODOs:
* Test MemOperation (gsecuredelete/mem-operation.vala:23).
  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 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)
  This affects all operations using paths, but in first place DeleteOperation
  that supports adding/removing of deletion targets.