From 2ec159e11e70650872319341095abfafad04ea9e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Eray=20=C3=96zkural?= <eray@pardus.org.tr>
Date: Tue, 14 Feb 2006 22:25:58 +0000
Subject: [PATCH] update todo and extend readme a bit

---
 README | 16 +++++------
 TODO   | 84 ++++++++++++++++++++++++++++------------------------------
 2 files changed, 49 insertions(+), 51 deletions(-)

diff --git a/README b/README
index d7c4db42..6dfaa15f 100644
--- a/README
+++ b/README
@@ -1,16 +1,16 @@
 PISI - Packages Installed Succesfully as Intended
 
-PISI is a new package manager implemented in python for the PARDUS
-distribution.
+PISI is a new package manager for the PARDUS
+distribution. In Turkish PISI means "kitty", and
+like a kitty, it is featureful and small.
 
 Some of its distinctive features:
 
- - Implemented in python.
+ - Implemented in python
  - Efficient and small
- - Package sources are written in XML and python.
- - Fast database access implemented with berkeley DB.
- - Integrates both low-level and high-level package operations.
+ - Package sources are written in XML and python
+ - Fast database access implemented with berkeley DB
+ - Integrates low-level and high-level package operations (dependency resolution)
  - Framework approach to build applications and tools upon
- - Comprehensive CLI and a user-friendly qt-based GUI (GUI
-   distributed separately)
+ - Comprehensive CLI and a user-friendly qt GUI (distributed separately)
  - Extremely simple package construction
diff --git a/TODO b/TODO
index a601a9c8..97b59349 100644
--- a/TODO
+++ b/TODO
@@ -173,20 +173,53 @@ Legend:
  * high priority
 
  + transaction stuff for database (eray)
-   + implement a simple (dandik) version for better reliability
  + database version file
 
- * medium priority
- 
- - component improvements (optional)
-   - maintain a list of components each component has
-   - maintain a list of packages 
+ * low priority
 
- * low priority 
- 
  + search command: (eray)
    + implement an inverted index
    + search in summary and description
+
+5. Post Release
+
+ * high priority
+
+ - high-level build commands
+   - build command enhancements:
+     - aware of repo sources
+     - full dependency analysis like install/upgrade etc.
+   - build-all (or build-distro) command, or as a separate tool
+   - an emerge command, just for fun
+ / make a package and sourcedb for each repo
+   + packagedb
+   - sourceb
+ - improve url support: consider adding "other" protocols
+   - removable media: media://
+ - examples:
+   - PSPEC i18n example for our great project with Bahadir :)
+
+ * medium priority
+
+ - UI impl: non-interactive use that selects defaults and logs output
+ - UI impl: a general purpose Qt UI
+ / multi-architecture support
+   + design decisions
+   + extend XML specs to support that
+   - cross-platform building support
+ - incremental build/fetch for repository index (pisi-index.xml)
+ - xdelta support (caglar)
+   - diffsets
+ - a command (check-repo) to check if repos are consistent wrt dep relations
+ - component improvements (optional)
+   - maintain a list of components each component has
+   - maintain a list of packages 
+ - more support for categories:
+   - put categories into a database
+   - fast search for categories
+
+ * low priority
+
  / overhaul installdb (try to merge its use with packagedb) (eray)
  / verify metodlari
    + SpecFile
@@ -199,41 +232,6 @@ Legend:
    - date type
    - enum type
    - make autoxml dependent on only xmlext and xmlfile interfaces
-
-5. Post Release
-
- * high priority
-
- - high-level build commands
-   - build command enhancements:
-     - aware of repo sources
-     - full dependency analysis like install/upgrade etc.
-   - build-all (or build-distro) command, or as a separate tool
-   - an emerge command, just for fun
- - more support for categories:
-   - put categories into a database
-   - fast search for categories
- / make a package and sourcedb for each repo
-   + packagedb
-   - sourceb
- - improve url support: consider adding "other" protocols
-   - removable media: media://
- - examples:
-   - PSPEC i18n example for our great project with Bahadir :)
-
- * medium priority
-
- - non-interactive use
- - multi-architecture support (baris, caglar)
-   / design decisions
-   / extend XML specs to support that
-   - cross-platform building support
- - incremental build/fetch for repository index (pisi-index.xml)
-   - diffsets (caglar)
- - a command to check if repos are consistent wrt dep relations
-
- * low priority
-
  - search command: (eray)
    - search components
    - english stemming