- Pacman-dev - lists.archlinux.org

[pacman-dev] [PATCH] pmdb_t: allow repo names to be longer than 128 chars
by VMiklos 22 Mar '06

22 Mar '06

hi http://darcs.frugalware.org/darcsweb/darcsweb.cgi?r=pacman;a=plain_commitdi…; any reason for limiting the length of the repo names? i would suggest increase the limit to PATH_MAX udv / greetings, VMiklos -- Developer of Frugalware Linux, to make things frugal - http://frugalware.org

2 2

[pacman-dev] cvs problems
by VMiklos 22 Mar '06

22 Mar '06

hi $ cvs update cvs [update aborted]: connect to cvs.archlinux.org(66.211.213.17):2401 failed: Connection refused is this a known problem? udv / greetings, VMiklos -- Developer of Frugalware Linux, to make things frugal - http://frugalware.org

2 2

[pacman-dev] [PATCH] pacman: query dbpath before using it
by VMiklos 21 Mar '06

21 Mar '06

hi http://darcs.frugalware.org/darcsweb/darcsweb.cgi?r=pacman;a=plain_commitdi…; fix for the ugly "DBPath: (null)" message when running pacman -v udv / greetings, VMiklos -- Developer of Frugalware Linux, to make things frugal - http://frugalware.org

2 1

[pacman-dev] [PATCH] alpm_db_update(): remove duplicated db->treename from path
by VMiklos 21 Mar '06

21 Mar '06

hi http://darcs.frugalware.org/darcsweb/darcsweb.cgi?r=pacman;a=plain_commitdi…; s|/var/lib/pacman/mypkgs/mypkgs|/var/lib/pacman/mypkgs| udv / greetings, VMiklos -- Developer of Frugalware Linux, to make things frugal - http://frugalware.org

2 1

[pacman-dev] [PATCH] _alpm_db_read(): fix install file's location
by VMiklos 21 Mar '06

21 Mar '06

hi http://darcs.frugalware.org/darcsweb/darcsweb.cgi?r=pacman;a=plain_commitdi…; so that pre/post_remove will work again udv / greetings, VMiklos -- Developer of Frugalware Linux, to make things frugal - http://frugalware.org

2 1

[pacman-dev] libalpm and backends
by Aurelien Foret 15 Mar '06

15 Mar '06

Hello, As a first step toward backend support, I slightly tweaked the database code from libalpm into this direction. Basically, I've moved all functions relating to the backend from db.c inside a new file "be_files.c". The idea is to have several distinct "be_XXX.c" files, one for each backend, implementing the hooks to access database fields. The functions that need to be implemented in order to write a new backend are: _alpm_db_open _alpm_db_close _alpm_db_rewind _alpm_db_scan _alpm_db_read _alpm_db_write _alpm_db_remove So, the next step should be to allow users to choose a backend with the configure script as follows ("files" is the default behavior): ./configure --backend=files or ./configure --backend=gdbm This option should impact the list of targets built in the libalpm library: if gdbm is activated, only the object "be_gdbm.c" should be compiled and linked inside the library. As of now, what is missing is to implement this selection in the configure.ac script and in the lib/libalpm/Makefile.am file. Currently, the Makefile.am is as follows: TARGETS = packege.o db.o cache.o list.o ... TARGETS += be_files.o This last line should be added conditionally depending on configure options. And the final big step is to revamp the sync db archives handling. To date, the database synchronization can't be easier: the library does not even need to read the archive, it simply unpacks it in /var/lib/pacman/<treename>. It works well because gensync archives are mapped on the current "flat files" database format. Now, let's imagine we're using a different backend... that can't work anymore: the library must read the archive, parse each entry and db_write it to the database. The following patch is implementing the whole thing: http://aurelien.foret.free.fr/archlinux/pacman/patches/pacman-lib-backend.p… Although the modifications are quite small and straightforward, I'm submitting this patch for review to the pacman-dev ml because it has an obvious external impact on sync db archives. Here are some explanations. To ease the pain, the idea is to rework gensync to simplify the sync db archive content. I reused the format from .PKGINFO files as used by makepkg and implemented it in gensync. For instance, in these conditions, an entry from the sync db archive is a file named "dummy-1.0-1" with the following content: pkgname = dummy pkgver = 1.0-1 depend = foobar1 replaces = foobar2 csize = 123456789 ... instead of a subdirectory "dummy-1.0-1" containing two files: dummy-1.0-1/desc: %NAME% dummy %VERSION% 1.0-1 ... and dummy-1.0-1/depends: %DEPENDS% foobar1 ... This way, it is possible to reuse the function parsedesc from package.c to parse both .PKGINFO files from package archives _and_ entries from database archives. IMO, this is quite efficient and simple: makepkg and gensync are using the same format, and gensync database archives are simpler to parse and analyze. Finally, I think pacman 3.0 is the right moment to implement it. We already agreed to break compatibility for sync databases by moving "replaces" and "force" fields from "desc" to "depends" db files, and as a consequence pacman 3 release will already require users to synchronize their sync databases before being able to use them. The gensync rework I'm suggesting will don't bring more hassle to the upgrade from pacman 2.9 to pacman 3.0. I'm interested to get feedbacks on the general idea and the implementation, before possibly committing it. -- Aurelien

2 3

[pacman-dev] [PATCH] fix the install file's location
by VMiklos 14 Mar '06

14 Mar '06

hi http://frugalware.org/~vmiklos/patches/libpacman-proposed/install_location.… ie. the location of the scriptlet of the pacman-tools package should be /var/lib/pacman/local/pacman-tools-0.6.8-1/install not /var/lib/pacman/pacman-tools-0.6.8-1/install udv / greetings, VMiklos -- Developer of Frugalware Linux, to make things frugal - http://frugalware.org

2 1

[pacman-dev] pactest 0.3
by Aurelien Foret 11 Mar '06

11 Mar '06

I've released a new version of the test suite. I've set up a small web page about the project: http://aurelien.foret.free.fr/archlinux/pactest/ This way I'll stop polluting the pacman-dev mailing list. Or may I add a "test" subdirectory in the CVS repository to put the testsuite in it? ;) -- Aurelien

3 3

[pacman-dev] [PATCH] --noscriptlet & PM_TRANS_FLAG_NOSCRIPTLET
by VMiklos 07 Mar '06

07 Mar '06

hi if you install packages in a chroot just as a dependency and remove them just after the build, then it worth to skip the pre/post_install/remove scriptlets http://darcs.frugalware.org/darcsweb/darcsweb.cgi?r=pacman;a=plain_commitdi…; this patch implements this for libalpm & pacman yes, the patch does not apply cleanly, there is a failed hunk, but Aurelien said before that's the a big problem so i won't fix it also probably the the value of PM_TRANS_FLAG_NOSCRIPTLET should be changed to 0x100 udv / greetings, VMiklos -- Developer of Frugalware Linux, to make things frugal - http://frugalware.org

2 1

[pacman-dev] TODO update
by Aurelien Foret 05 Mar '06

05 Mar '06

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

2 6