-
Notifications
You must be signed in to change notification settings - Fork 41
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
Please provide LICENSE or COPYRIGHT file #70
Comments
Also, please consider tagging a stable release :-) At the moment the best I can do is provide a Debian-specific "upstream/1.5+git20180312.068218d-1" version, but updating |
Hi @andschwa, I read these :-) which was why I was able to begin work on packaging eproject for Debian, and why I'm confident in PR #71 (which is GPL-3+ @ the second commit). I believe that the Emacs library conventions were probably written before best practises including a full-text copy of the license emerged, and additionally I wonder if Emacs library conventions are written from the point of view that the most useful libraries should eventually end up as part of the Emacs project itself--which has a full-text copy of the license. A GNU document on the topic is here https://www.gnu.org/licenses/gpl-howto.en.html Please provide a full-text copy of the GPL-3+ license. In good faith I went ahead and examined every file in eproject with a fine-toothed comb, wrote the Debian copyright file (log/analysis) and packaged an untagged snapshot. Luckily an ftp-master did not reject the upload, but instead conditionally accepted it with a note to pursue clarification of eproject-as-a-whole license...also in good faith, even more so because packaging git snapshots are not considered best practise in Debian. BTW, this one still asserts GPL-2+ Line 16 in 068218d
in conflict with Line 8 in 068218d
|
Dear eproject maintainer,
Thank you for maintaining this package. I would like to package eproject for Debian, but the absence of a LICENSE or COPYRIGHT file blocks inclusion into the archive.
Cheers,
Nicholas
The text was updated successfully, but these errors were encountered: