aboutsummaryrefslogtreecommitdiff
path: root/TODO
diff options
context:
space:
mode:
authorvolpino <fox91@anche.no>2012-11-26 15:38:27 +0100
committervolpino <fox91@anche.no>2012-11-26 15:38:27 +0100
commit7380daf7e9c3fdd6f20442706fc1f5eb832584ec (patch)
tree29acad6194b8e8d271e092e3584de466ed0881c1 /TODO
parenteuscanwww: per handler package list (diff)
downloadeuscan-7380daf7e9c3fdd6f20442706fc1f5eb832584ec.tar.gz
euscan-7380daf7e9c3fdd6f20442706fc1f5eb832584ec.tar.bz2
euscan-7380daf7e9c3fdd6f20442706fc1f5eb832584ec.zip
euscanwww: Fixing metadata and ebuild urls
Signed-off-by: volpino <fox91@anche.no>
Diffstat (limited to 'TODO')
-rw-r--r--TODO9
1 files changed, 3 insertions, 6 deletions
diff --git a/TODO b/TODO
index b227356..f2fbd7d 100644
--- a/TODO
+++ b/TODO
@@ -24,8 +24,8 @@ euscan
### metadata.xml
-- Create a page to list handlers users, and average confidence
-- Use this page to generate metadata for some packages (handled by deb or brute force for example)
+- Use handler's statistics page to generate metadata for some packages
+ (handled by deb or brute force for example)
- Create a subtree of metadata using custom rules
- Finalize format
- Write a GLEP
@@ -40,7 +40,7 @@ euscan
### handlers
- remote-id type deb repository:
- - find out how to get download url (not sure it's possible)
+-- find out how to get download url (not sure it's possible)
### remote-id
- Propose new remote-id: deb
@@ -56,15 +56,12 @@ euscanwww
### misc
-- change ebuild/metadata urls. Use <overlay>/<category>/<package>-<version>(-<revision>?).ebuild instead. Use portage code to parse that. Same thing for metadata.xml, without
- version-revision.
- Really fix mails: better formating
- Always keep in db all found versions (when using an API only?). But don't display them if older than current packaged version, except maybe in the "upstream_version" column.
### packages
- show additional informations in the web interface (remote-id, etc...)
-- show the content of the ebuild for a particular version
- Ignore alpha/beta if current is not alpha/beta: per-package setting using metadata.xml ?
- ~arch / stable support: see "models: keywords"
- stabilisation candidates: check stabilizations rules, and see how this can be automated