diff options
| author | Roger Dingledine <arma@torproject.org> | 2008-12-13 06:39:53 +0000 |
|---|---|---|
| committer | Roger Dingledine <arma@torproject.org> | 2008-12-13 06:39:53 +0000 |
| commit | 46cb963aec7455e8ff31c824ceaeccb7d37e7f1f (patch) | |
| tree | c918dc5a237ec61d3e3dd7b3432f683ff89ab856 | |
| parent | f63e0bb285beecf14b2017046f8855291d4fd431 (diff) | |
client-side thandy caches just grow without bound. this might
actually not be a good idea.
git-svn-id: file:///home/or/svnrepo/updater/trunk@17615 55e972cd-5a19-0410-ae62-a4d7a52db4cd
| -rw-r--r-- | TODO | 8 |
1 files changed, 8 insertions, 0 deletions
@@ -7,6 +7,14 @@ o Decouple install from check: they are not necessarily related. - Better version comparison. +- <arma> should thandy auto-clean its cache? should there be a new 'thandy + clean' way to call it? should it be a command-line option, on by + default? the last one seems best. + <edmanm> after a successful install, i would think thandy could just + remove the installer. unless we want to keep it around for repairs + or something. even then, after a succesful install, it might as well + automatically remove all packages older than the one it just installed. + - Security stuff that we should do 1 Check SSL certs or something in urllib2. Not that Thandy really cares about repositories getting mitm'd. |