-
Notifications
You must be signed in to change notification settings - Fork 5
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 avoid including generated code as part of source #32
Comments
|
Preferrably both: I would assume that the build routines used to generate documentation can be easily extended to also generate the needed png files. |
I'm not familiar with them either. But I'll look into #33 . |
There is no single universal "wrong", so it depends on what you want, really. If you don't want to streamline the packaging, to separate source from generated artifacts, then I will stop wasting both of our time, and stop trying to help you get your project into shape for CPAN distribution. Possibly your style of managing your code is still suitable for acceptance with CPAN, I don't really know. I do know that your style of managing code is not acceptable for Debian, but there I can circumvent your bloat and potential licensing problems locally. |
The project contains files that are not "the preferred form of the work for making modifications to it", as the GPL license defines source code to be.
Please consider tracking only source with git, and then maybe when issuing releases not only issue source releases but also use some Github mechanisms (which I am not familiar with, just notice exists) to release generated files.
The text was updated successfully, but these errors were encountered: