[pacman-dev] Future pacman development (3.2/4.0)

eliott eliott at cactuswax.net
Fri Aug 31 16:27:29 EDT 2007

On 8/31/07, VMiklos <vmiklos at frugalware.org> wrote:
> Hello,
> Na Sat, Aug 25, 2007 at 03:25:33PM +0200, Xavier <shiningxc at gmail.com> pisal(a):
> > I don't really have any strong opinion on this.
> > But now vmiklos got some backup :p
> :P
> having the config parser in the frontend is a very very bad idea imho,
> just i don't want to flame on this list all the day ;)

Actually, the config parser SHOULD be in the frontend.

libalpm is a library. Libraries don't generally parse configs. They
receive config values through the api, at run time.

pacman is effectively a front end for libalpm. Thus, pacman should
parse the pacman.conf config file.

There could certainly be a configuration parsing library, that
front-ends can share, but it doesn't need to be tied into libalpm.
That should just handle package management.

More information about the pacman-dev mailing list