Skip to content


Subversion checkout URL

You can clone with
Download ZIP


Licensing makes it hard to include in distributions #19

stapelberg opened this Issue · 5 comments

2 participants



I’d like to package dunst for Debian so that people don’t have to follow a strange tutorial and can enjoy apt-get install dunst instead.

However, your licensing is a bit problematic :-/. As you might know, beerware is not exactly a license which Debian considers free. Would it be an option for you to provide a clear LICENSE file and use one of the licenses which are already present in your code? For example MIT/X11 from dmenu, or the BSD license from inih.

That’d be great!
Best regards,



a debian package would be great.

My knowledge about licenses and their implications is pretty low, so I don't know if I can just choose one license when there's code under another license as well. If you already know (or have a link handy) whether and how I can do that and what I have to do in order to proper document the license that would be great and make things faster.

edit: with the latest changes I pushed shortly before you wrote, the tutorial isn't necessary anymore. But that doens't change the fact, that I would love to see a debian package :-)


Thanks for your reply.

Since you are the code author, you can chose the license you want to distribute it under.

One accepted way to go is to place a copyright notice in your (!) files, looking like this:

/* copyright 2012 Sascha Kruse and contributors (see LICENSE for licensing information) */

In the file LICENSE you then state:

All files (unless otherwise noted) are licensed under the BSD license:

followed by the text of the BSD license, you can find it at for example.

It’d make things even more clear if you add a similar notice to other files which are licensed differently (like files you took from dmenu).

Feel free to ask if you still got any questions about this.


could you please take a look at the "license" branch? I'll merge it into master if everything looks fine.

Thank you.


Looks good to me! Thanks.


Merged into master, thank you.

Feel free to open new issues, if there are other things that I can do to make your life as a packager easier.

@knopwob knopwob closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.