-
Notifications
You must be signed in to change notification settings - Fork 31
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
Update the MANIFEST.in file #240
Conversation
Is the draft status on purpose? |
Yes, I'm not 100% sure which files should be included or excluded. But if it looks good to you or you think this is harmless (better more than not enough), feel free to mark as ready and merge. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm also unsure of what to ship but the developer-tool related files should probably be ignored. I had no idea that this file existed or what it's used for so I don't really have an opinion apart from that.
Also, it seems to me that this is including #239, so you should add @brainexe as co-author. He's also more likely to have a better insights on this than me :)
c07326e
to
5cccc9d
Compare
FTR I checked on upstream debian package for powa-web, and apart from the setup.py |
I just rebuilt the version with the new manifest and it looks all good, needed files are all present for me. 👍 |
We include built asset files (in static/dist). We exclude files that are only useful for dev. We also add a CI job to check the Manifest. Co-authored-by: Matthias Dötsch <[email protected]>
5cccc9d
to
f6cd7d7
Compare
No description provided.