Hello, I've closed items: [3] code synchro with pacman 2.9.8 [5a] db_write: database entries cleanup [11] _alpm prefix to private library functions On-going items: [7] (vmiklos) [8] (aurelien) the .lastupdate code was moved from the library to the frontend. FYI, I'm currently working on item [6] Here is the updated TODO: [2] possible db corruption because of pmsyncpkg_t struct: the spkg field is just a pointer to data from the cache, which is likely to change during sync_commit [5] database cleanup b) do not add name and version entries in "desc" file (already available in the directory name), and also for .PKGINFO file (in makepkg)? => on hold for now [6] more debug messages in libalpm some parts of the code still remain obscure (file conflicts handling for instance) even when running pacman with "--debug=-1" [7] remove exit() calls from libalpm the library should never call exit() but always return an error code to the frontend (for instance, drop MALLOC macro) [8] .lastupdate review Is the .lastupdate file really needed? Using mtime isn't enough? [9] review file conflict code See this thread: http://www.archlinux.org/pipermail/pacman-dev/2006-February/000202.html [10] pacman -Sw Outputs are wrong compared to pacman 2.9 Do not use log callbacks when the -w is used? or filter all outputs in trans.c depending on the downloadonly flag? => it should be done as the last step before a first release to avoid introducing too much changes to the CVS code at once. -- Aurelien