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

VMiklos vmiklos at frugalware.org
Fri Aug 31 20:08:28 EDT 2007


Na Fri, Aug 31, 2007 at 01:27:29PM -0700, eliott <eliott at cactuswax.net> pisal(a):
> Actually, the config parser SHOULD be in the frontend.

wrong. for example we have gfpm, a graphical frontend. having only a
signle parser in libpacman to parser the configured repos is great, and
i think all the users would be unhappy if they would have to always
update gfpm's config accordingly

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

really? just think of libsasl's /usr/lib/sasl2/smtpd.conf

> 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.

yes, of course. then please remove -ldownload from libalpm's LDFLAGS

- VMiklos
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://archlinux.org/pipermail/pacman-dev/attachments/20070901/7baa9fd3/attachment.pgp>

More information about the pacman-dev mailing list