Michael Stapelberg <stapelb...@debian.org> writes: >> > Nevertheless, I would still like to ask: why? Does anything depend on >> > this, any potential users that couldn't use something simpler? >> > (There's another ini parsing library, also in C, in about 100 lines >> > of code instead of 1500, that does pretty much everything this one >> > does, and is far less scary.) > There is a lightweight notification daemon called dunst which depends on > this. I’m going to file an ITP for that soonish: > http://knopwob.github.com/dunst/
I see. Wouldn't it be a better idea to replace the iniparser dependency of dunst with something saner? :) I'm willing to submit a patch to replace iniparser with inih[1], anything to keep iniparser out of Debian, as that thing is the poster child of brokenness. [1]: http://code.google.com/p/inih/ -- |8] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
