[pacman-dev] CVS update of pacman-lib (TODO.dan)

dan at archlinux.org dan at archlinux.org
Tue Jan 30 02:35:51 EST 2007

    Date: Tuesday, January 30, 2007 @ 02:35:51
  Author: dan
    Path: /home/cvs-pacman/pacman-lib

   Added: TODO.dan (1.1)

adding my personal TODO file

 TODO.dan |   64 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 64 insertions(+)

Index: pacman-lib/TODO.dan
diff -u /dev/null pacman-lib/TODO.dan:1.1
--- /dev/null	Tue Jan 30 02:35:51 2007
+++ pacman-lib/TODO.dan	Tue Jan 30 02:35:51 2007
@@ -0,0 +1,64 @@
+This is my personal TODO list. No guarantees if it is out of date and things
+  no longer apply. If you want to help out with any of it, send me an email.
+* Variable names in makepkg.conf--confusing
+  - some use 'USE_', others do not
+  - some are 'NO', some are 'KEEP', etc.
+  - some options use 0/1, others are y/n
+* Should undocumented makepkg (and thus PKGBUILD) options be put in the
+  manpage, as well as including sections for them in the makepkg.conf file?
+* Go through all makepkg bugs in flyspray and see if they are rectified:
+  http://bugs.archlinux.org/index.php?tasks=&project=1&string=makepkg
+* Documentation- no one likes to write it, but everyone reads it. Work on the
+  man pages and make sure they are up to date.
+* doc/PKGBUILD.5- continue cleanup work
+* PKGBUILD man page should be in section 5 and not section 8
+* Port the libdownload (libfetch) manpage from BSD style to Linux style, or at
+  very least change references to BSD.
+* Revise build system to a more static one (Aaron mentioned wmii system).
+* NEWS file updating and cleanup. Get rid of items that are bugfixes of never-
+  released code, etc.
+* New cache cleaning functionality in pacman - keep installed version, choose
+  number to keep, etc. Good python script in the forums that we should try to
+  emulate, perhaps.
+* pacman - downgrade feature - allow users to see cached packages andi
+  downgrade to (previous or any?) available options.
+* alpm_log_action & install script logging interaction - producing duplicate
+  entries in pacman logs (possibly fixed? needs more testing but looks good)
+* Extreme similarity between some of the sync and add code...we have to be able
+  to abstract more away from sync actions and add actions to just 'actions'
+  (example: sync,c, add.c, and deptest.c all contain a switch on PM_DEP_MOD_*)
+* Merge update, add, and sync code when possible, so we reduce duplication.
+* For Pacman 3.1 - List every function, define, etc. in libalpm. Give one
+  sentence description of each. If it sounds like two are similar, find a way
+  to combine or refactor them. If it is unnecessary- delete it. Stop keeping
+  everything clustered in little add/sync/remove parts, allow transactions to
+  share code.
+* Pacman 3.1 - Go through options list. Decide if namings are good, all options
+  are still relevant, etc. Ideas for -Re (#6273), changing meaning of -c (has
+  two meanings, another FS bug), etc. 
+* Monotone suggestion- allow changing of a branch name after commit (example:
+  I meant to commit to a new branch, but I forgot --branch option on the
+  commit.  Can I remove the original branch cert and replace it with a new
+  one?)
+Quick hits:
+* log_progress and cb_trans_progress - same function? not quite but commonality
+* unsigned int vs. unsigned
+* 'ldd' & 'ldd -u' - many linkages
+* possibly split utilities/extras from pacman package
+* makepkg3 produces files with arch appended- gensync can't deal with it
+* Fix repo-add script so it replaces packages instead of simply adding new onesi
+  (so old version is properly removed).

More information about the pacman-dev mailing list