The lockfile (path) basically should not be part of the client. There can be multiple user agents accessing alpm for installing, even parallel, what could cause troubles.
Therefore, locking alpm is a quite good thing (actually).
Anyway, i'm looking up code in pacman git, yes, but currently have the latest "normal" alpm version installed.
I won't install always the latest git version of pacman/alpm on my system, since this can really cause big troubles.
Anyway, i'm setting databases and similar, so i know the configuration is moved out of alpm towards pacman. Also, i wouldn't see a problem providing the lockfile location as a configure option, setting a default.
Anyway, the option is undocumentated. I've just been wondering, since the package yaz probably has nothing to do with my configuration.
I got this error on adding any package, when a newer version was available of qtcurve (which was in IgnorePkg) and i havn't had installed it yet. Anyway, i didn't set the sync flag (y), just the option (S), so i don't think it should matter.
Yours,
Georg (STiAT)
On 6/21/07, Xavier <shiningxc@gmail.com> wrote:
2007/6/21, Georg Grabler <ggrabler@gmail.com>:
>
> - I thought configuration handling is now done by pacman
> - Do i need to set the IgnorePkg of alpm for some reason?
> - I have no idea why this can fail.
>
Are you using pacman git ?
If you're using only the libalpm part of pacman git, then you should
have noticed you need to do the configuration part yourself. For
example, pacman segfaults if the lockfile isn't set.
_______________________________________________
pacman-dev mailing list
pacman-dev@archlinux.org
http://archlinux.org/mailman/listinfo/pacman-dev