-
Notifications
You must be signed in to change notifi 8000 cation settings - Fork 161
Generate debian/copyright files #926
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
Comments
I use the "missing license" output from the console and then make one by hand. Certainly the data's there. Harder problem would be managing it long term (and finding unused paths, etc.). Would definitely be handy, though! |
What do you mean with "managing it long term"? I would expect you could just regenerate the copyright file for every release and avoid making manual changes to that file. Or do I overlook something? |
I'm not sure this will be built in, but you could very easily run |
Thank you for your time and contributions! Unfortunately, this issue has been inactive for quite a while which means we probably can't manage the time to deal with it. That's why we're marking it as stale. We want to keep things tidy and focus on active discussions, but we’re always happy to revisit if this is still relevant! If you’d like to keep this open, please add a comment to let us know and remove the label stale. Otherwise, this issue will most likely be automatically closed soon. |
Since there hasn't been any recent activity after the last message, we're going to go ahead and close this issue. Feel free to reopen this and remove the labels stale and unresolved if it's urgent. We truly appreciate your contributions and engagement! Thank you and happy hacking! |
Hi,
is there any easy way to reuse ( ;-) ) the copyright information processed by reuse to generate debian/copyright files (https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/) so we do not have to maintain that file manually?
Thanks,
Florian
The text was updated successfully, but these errors were encountered: