| index : pacman | |
| Archlinux32 fork of pacman | gitolite user |
| summaryrefslogtreecommitdiff |
| -rw-r--r-- | TODO.aaron | 16 | ||||
| -rw-r--r-- | TODO.dan | 17 |
@@ -1,23 +1,11 @@ == This is my custom TODO file == -** THIS IS A TEST COMMIT - * transaction object should contain two package list (install and remove) instead of a single list of syncpkgs - this should allow us to get rid of that type. This also requires seperate functionality to return a list of "replaces" packages to the front end, so the frontend can handle the QUESTION() stuff in that case -* Look into other VCSs to use. The main CVS repo will remain, but having a - distributed system to allow for easy patching/pushing/pulling would be nice - - monotone and mercurial look like the top contenders in my book, but I need - to evaluate both a bit more. - -* src/pacman: - There's quite a few single function headers which contain the pacman_* - functions. We should move these to a single header (pacman.h) to clean up - the source a bit. - * libalpm -> front end communication needs a work-up. Both progress functions can be combined into one callback, IFF we adjust it to accept a prefix string for the progress bars, and format it at the lib side. Question functions @@ -47,10 +35,6 @@ * pacman: fixup doxygen documentation for public interface -* libalpm: just because a function is in alpm.h doesn't mean it needs to be in - alpm.c - we should move functions around where they should be. In fact, - alpm.c might not be needed at all, if things were organized properly. - * feature for 3.1: package file hooks * I've been planning on this one for some time. Here's a simple rundown: in /etc/pacman.d/hooks: @@ -46,12 +46,6 @@ another FS bug), etc. Remove the -A flag and possibly -D, -T, and -Y (-Y is killed now in favor of vercmp binary) if they can be done by other actions. Possible switch of -U --> -I (#5571). -Rewrite _alpm_sortbydeps to use Topological Sort. Should work using a standard -topo sort algorithm, once the crazy types can be fixed up a bit. Include a -cycle check - print a big error message if this happens. - -- http://en.wikipedia.org/wiki/Topological_sort - -- http://everything2.com/?node_id=556079 - Review display and logging functions. There seems to be an abundance of them. Make it extensible to use color, review what verbose/debug means. Perhaps separate logging functionality- Pacman has its normal log, and alpm backend @@ -59,12 +53,6 @@ keeps a very simple log file - listing only adds (including syncs) and removes. This way a consistency list can be kept of what is currently installed and what isn't, without all the logging junk from the front end. -If we stick with autotools, add more defines to configure.in, including -CACHEDIR, PKGEXT, so these can be specified at configure time for ease of use -by other distributions which may want to change the defaults. Also, review what -needs to be in config.h and what does not. There may be excess #depends which -are hard coded into the sources. (from TODO.autoconf) - Profile the code. Find the functions that are being called a lot, and see what can be done about it. Find out if all these calls are necessary (e.g. excessive alpm_list_count calls), and maybe think about changing data structures to speed @@ -86,11 +74,6 @@ including all pacman utilites- abs, pacman-optimize, etc. Bugs/FRs to smash: 6468, 6437, 6430?, 6420, 6404, 6389, 6312?, 6284, 6273?, 6255?, 6208, 5987, 5885, 5571, 4182, 3492, 2810?, 1769, 1588, 1571 -Remove _alpm from function names now that we have SYMHIDDEN and static -declarations. - -Remove alpm.c, put functions where they should be. - Update doxygen comments, they may need some work. Try to document all of the private internal functions too- it helps a ton for people just getting a start on pacman hacking. |