[pacman-dev] Pacman configuration parser library

[Jelle van der Waa]

On 01/01/17 at 11:34pm, Andrew Gregory wrote:
> On 01/02/17 at 09:10am, Allan McRae wrote:
> > On 02/01/17 06:48, Xyne wrote:
> > > Happy new year!
> > > 
> > > It would be useful for third-party developers to have access to the Pacman
> > > configuration file parsing functions and datatypes in src/pacman/conf.h. Would
> > > you consider providing a shared library for this (or adding it to libalpm)? It
> > > would be more reliable than third-party custom parsers.
> > > 
> > > Aside from providing the actual shared object file, the only change needed*
> > > would be to remove the lines from parseconfig (conf.c) that free config->repos
> > > so that users could access repo information directly via config->repos after
> > > invoking the function (config_free will free that memory later).
> > > 
> > 
> > This is on the todo list (along with adding pacconf for easy access to
> > the configuration from scripts).
> > 
> > I don't think anyone is actively working on it...
> > 
> > A
> 
> I don't particularly care about providing a config parsing lib with
> pacman and have no desire whatsoever to figure out how to get
> autotools to make such a lib.  If it's something we're going to do
> though, it would probably make sense to just incorporate the pacutils
> parser.

I'd like to chime in that I would love to see pyalpm to stop using it's
self written config parser. I've put it on my TODO list, but I'm not
sure when I'll be able to look at it.

-- 
Jelle van der Waa
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <https://lists.archlinux.org/pipermail/pacman-dev/attachments/20170102/7c40b542/attachment-0001.asc>