Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate dunst from iniparser to inih. #18

Closed
wants to merge 1 commit into from
Closed

Migrate dunst from iniparser to inih. #18

wants to merge 1 commit into from

Conversation

algernon
Copy link
Contributor

Instead of using iniparser, which is rarely packaged, and is an external dependency, use an embedded copy of inih instead, which is only a hundred or so lines, and can do pretty much the same as iniparser.

The benefit is one less external dependency, and it makes it easier for distributions to package dunst.

This also fixes issue #12.

Instead of using iniparser, which is rarely packaged, and is an
external dependency, use an embedded copy of inih instead, which is
only a hundred or so lines, and can do pretty much the same as
iniparser.

The benefit is one less external dependency, and it makes it easier
for distributions to package dunst.

Signed-off-by: Gergely Nagy <algernon@balabit.hu>
@knopwob
Copy link
Member

knopwob commented Jun 20, 2012

Did you use 2 different editors to write this? Because it's a mixture of tabs and spaces. It's not a problem; I'm just curious how this happend.

Other than that everything looks fine. I've pulled (locally) and fixed the issues above. If I don't encounter any problems, I'll merge this into master soon. I'll also add a AUTHORS file; how would you like to be mentioned there?

@algernon
Copy link
Contributor Author

As for the editor, I used only one, but forgot to set it to only use spaces, and it defaulted to using a mixture when I told it not to use GNU-style indentation. Sorry about that!

Regarding the AUTHORS file: I don't think it's necessary to mention me there, it's a tiny little patch, and attribution in git log is good enough for me. But if you want to, whatever I used for the Signed-off-by is good.

@algernon
Copy link
Contributor Author

Since you merged this, and touched it up, lets close the pull request too! :)

@algernon algernon closed this Jun 21, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants