[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Need opinion on a configuration parser library

You could provide a compile time option either to use built-in parser for those distros allow that or external one for those that don't (like Fedora in your example).
As for my own project, I use own INI format parser since I extended the format a bit.

2014-07-10 18:22 GMT+07:00 Alexandre Dantas <eu@alexdantas.net>:
Hello, everybody!
I'm the upstream and current maintainer for nsnake (a ncurses clone
of the snake game) and would like to know your opinion on this
packaging matter.

I was in need of a library that helped storing per-user configuration
files on that game.
So I started using libiniparser[0] on the hope that it would make the
game portable across most distros. Unfortunately, it was only after
nsnake's 2.0.0 release that I realized it wasn't available on Debian.
(and probably won't be at all[1])

This ends up preventing me from updating the package on Debian.

So could you guys recommend any configuration-file parsing library
that's both maintainer-friendly and portable across distros?

Of course I may be over-thinking this - I considered simply bundling
inih[2] to my code (rougly 100 lines of C code), just like owncloud[3]
and dunst[4] both did.
But the Fedora guys advised me against that[5], since they're very
strict on "no bundled libraries".

I guess I could simply hard-code a parser for config files, but it seems
as kind of a bad practice... Hopefully I'm wrong and you guys could
shed a light on this problem.

Thank you all for the attention,
Alexandre Dantas

[0]: http://ndevilla.free.fr/iniparser/
[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582657#10
[2]: https://code.google.com/p/inih/
[3]: https://open.cryptomilk.org/issues/5
[4]: https://github.com/knopwob/dunst/issues/12
[5]: https://bugzilla.redhat.com/show_bug.cgi?id=1075154#c2

Reply to: