Re: [Zope3-dev] Zope 3.4, eggs and windows
Am Samstag, den 21.04.2007, 22:20 +0200 schrieb Martijn Faassen: Hi there, I have some questions about the Zope 3.4 release. My apologies if this information is already available somewhere else. I've just uploaded z3c.widget to download.zope.org/distribution, but ran into a new snag: it properly lists a whole bunch of dependencies in its setup.py that are currently Zope core packages, and thus post-3.3. I'm still developing against Zope 3.3 and using z3c.widget would therefore lead to a mix of Zope 3.3 and post 3.3 (3.4) packages in my installation. It's like to avoid this. Is there is a way to suppress the automatic download of dependencies for a particular egg in buildout? A manual hack is to upload a private version of z3c.widget somewhere that has a different dependency list and then refer to that. Instead of hacking, I could also decide to start relying on an eggified Zope 3.4 right away. I've heard some discussion though that makes me wonder whether an eggified release of Zope 3.4 will be fully cooked. I'm using the pre 3.4 eggs in some projects and they work fine. This leads to some questions: * I don't believe the 3.4 alpha eggs have been uploaded anywhere yet, right? Right. There was discussion about automation for that. I'm currently spending some time working on Zope bugs, but I might switch over to do those releases. Christian -- gocept gmbh co. kg - forsterstraße 29 - 06112 halle/saale - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Zope 3.4, eggs and windows
Hi, I took Martin's script and adapted it for this release. I took the listing of download.zope.org and gathered the names of all eggs that were available as 3.4dev eggs and am currently creating 3.4.0a1 eggs for those. It might be that these are not all eggs that should be build. However, doing an egg release for a package that is on zope.org is simple and quick now: Get the 'release-egg.sh' script from Zope3/trunk/releases/ and run it with 'release-egg.sh packagename version'. The script then - creates a tag for the release - checks out the release - changes the version parameter in setup.py - checks this in - runs setup.py sdist - uploads the tarball to download.zope.org I'll modify the script in the future if we get more complex requirements. Martin's original script already handled some cases that I didn't need right now, so I removed them for the moment (using a branch, ...) Christian -- gocept gmbh co. kg - forsterstraße 29 - 06112 halle/saale - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Zope 3.4, eggs and windows
The eggs are released now. I do not have updated the externals to the right location, the actual released code came from the Zope 3 trunk but is identical to the release. I noticed that after the fact that I made the release. :/ Updating the externals needs a little more effort to automate, but I'll do that later today. Christian Am Sonntag, den 22.04.2007, 12:38 +0200 schrieb Christian Theune: Hi, I took Martin's script and adapted it for this release. I took the listing of download.zope.org and gathered the names of all eggs that were available as 3.4dev eggs and am currently creating 3.4.0a1 eggs for those. It might be that these are not all eggs that should be build. However, doing an egg release for a package that is on zope.org is simple and quick now: Get the 'release-egg.sh' script from Zope3/trunk/releases/ and run it with 'release-egg.sh packagename version'. The script then - creates a tag for the release - checks out the release - changes the version parameter in setup.py - checks this in - runs setup.py sdist - uploads the tarball to download.zope.org I'll modify the script in the future if we get more complex requirements. Martin's original script already handled some cases that I didn't need right now, so I removed them for the moment (using a branch, ...) Christian ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/ct%40gocept.com -- gocept gmbh co. kg - forsterstraße 29 - 06112 halle/saale - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
