You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think the only things missing are the stylesheets and po files.
As to why those aren't there, I'm not sure. Apparently I'm not clear on how setuptools processes the MANIFEST file. I thought it included all files in the directory by default, but apparently it doesn't.
This may be completely incorrect and wrong (I'm very new to setuptools stuff), but this appears to get the missing po files and stylesheets into the sdist tarball:
diff --git a/MANIFEST.in b/MANIFEST.in
index 83864f2..0576a89 100644
--- a/MANIFEST.in
+++ b/MANIFEST.in
@@ -1,5 +1,7 @@
include .gitignore
include data/terminator.appdata.xml.in data/terminator.desktop.in
+include po/*
+include terminatorlib/themes/*/*/apps/*.css
include tests/*
include INSTALL.md README.md
exclude po/.intltool-merge-cache
Yeah, I think that's right, but I think we're just gonna go with the git archive command for generating the tarball, rather than the setup.py sdist command
Activity
mattrose commentedon Dec 31, 2020
We could just do a 2.1 release with the necessary artifacts.
The tests that we have are in 2.0.1. I thought the icons and stylesheets were in there too, but I may be wrong.
mattrose commentedon Dec 31, 2020
This is what's currently generated by
python setup.py sdistI think the only things missing are the stylesheets and po files.
As to why those aren't there, I'm not sure. Apparently I'm not clear on how setuptools processes the MANIFEST file. I thought it included all files in the directory by default, but apparently it doesn't.
lazyfrosch commentedon Dec 31, 2020
I see we have a bunch of commits, so maybe useful ð
I'm not very familiar with sdist, but IMHO the tarball of sdist should include everything plus generated metadata.
mattrose commentedon Dec 31, 2020
Thanks for the compliment on the release ð It only needed one do-over ð
lazyfrosch commentedon Dec 31, 2020
I would generate the artifact like this:
Main purpose of the artifact is to have a signed tarball, the tarball is the same as GitHub would generate it.
mattrose commentedon Dec 31, 2020
Oh, let me try that.
lazyfrosch commentedon Dec 31, 2020
We only need to document it in RELEASE.md
mattrose commentedon Dec 31, 2020
Do you want to updeate the RELEASE file? Then we can close this.
zothar commentedon Dec 31, 2020
This may be completely incorrect and wrong (I'm very new to setuptools stuff), but this appears to get the missing po files and stylesheets into the sdist tarball:
mattrose commentedon Dec 31, 2020
Yeah, I think that's right, but I think we're just gonna go with the
git archivecommand for generating the tarball, rather than thesetup.py sdistcommandUpdate RELEASE docs
Update RELEASE docs
py-terminator: Upgrade to 2.1.0
py-terminator: Upgrade to 2.1.0
py-terminator: Upgrade to 2.1.0
py-terminator: Upgrade to 2.1.0