[pacman-dev] libalpm and backends

VMiklos vmiklos at frugalware.org
Tue Mar 14 19:54:23 EST 2006


On Wed, Mar 15, 2006 at 12:33:00AM +0100, Aurelien Foret <aurelien at archlinux.org> wrote:
> You can hardly compare the libarchive and the backend things.
> 
> Replacing libtar by libarchive is purely an internal change. Users won't 
> even notice it. It could be done at any time, in any release. It does 
> not matter.

http://www.archlinux.org/pipermail/pacman-dev/2005-October/000009.html

i thought based on that mail that you won't do it before 3.0. which is
quite different from _any_ time :)

> Anyway, my first mail was maybe not clear, but there's only one thing my 
> patch is about: implementing correctly the sync database upgrade, by 
> taking the opportunity of pacman 3 release to do it without additional 
> troubles for users.
> This will get ride of the "ORE" tag in alpm.c:alpm_db_update.
> And AFAIK, _this_ is on the TODO.

ok, thanks for the clarification. i thought you would start to work on a
whole gdbm implementation ;)

udv / greetings,
VMiklos

-- 
Developer of Frugalware Linux, to make things frugal - http://frugalware.org




More information about the pacman-dev mailing list