Skip to content
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

Upload tar.gz for sdist #51

Open
koobs opened this issue Jan 30, 2015 · 6 comments
Open

Upload tar.gz for sdist #51

koobs opened this issue Jan 30, 2015 · 6 comments

Comments

@koobs
Copy link

koobs commented Jan 30, 2015

One less dependency in the FreeBSD port

<3

@tomster
Copy link
Contributor

tomster commented Mar 6, 2015

@fschulze what was the patch for mkrelease again? i want to incorporate from 2.0.1 onwards :)

@fschulze
Copy link
Member

fschulze commented Mar 6, 2015

diff --git a/jarn/mkrelease/mkrelease.py b/jarn/mkrelease/mkrelease.py
index 73d4915..6b52b52 100644
--- a/jarn/mkrelease/mkrelease.py
+++ b/jarn/mkrelease/mkrelease.py
@@ -232,7 +232,7 @@ class ReleaseMaker(object):
         self.scmtype = ''
         self.distcmd = 'sdist'
         self.infoflags = ['--no-svn-revision', '--no-date', '--tag-build=""']
-        self.distflags = ['--formats="zip"']
+        self.distflags = ['--formats="zip,gztar"']
         self.directory = os.curdir
         self.scm = None

@koobs
Copy link
Author

koobs commented Mar 7, 2015

\o/

@koobs
Copy link
Author

koobs commented Oct 28, 2015

@tomster Bump on this, its now 2.1.0 ;)

@tomster
Copy link
Contributor

tomster commented Dec 2, 2015

@fschulze i really don't want to maintain a patched version of mkrelease - either we should get lurker to make a new release or we should fork mkrelease and include that in bsdploy's development dependencies (but then we would need to do that for all ploy_*, too.

what do you think is best?

@fschulze
Copy link
Member

fschulze commented Dec 2, 2015

I'm tending towards using "devpi upload", which supports selection of release types via setup.cfg. But then we have to take care about pushing release tags ourself.

In the hopefully not too distant future it's automated to create releases on our own devpi server and we just push to pypi when ready.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants