-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Stefan H. Holek wrote: > On 19. Sep 2007, at 00:46, Jodok Batlogg wrote: > >> i'm wondering why i couldn't fine zope.app.wsgi = >> 3.4.0b1dev_r75415 after 3.4.0 was released a few days ago. >> probably someone in [philikon, ctheune, J1m, baijum] removed the egg? >> we nailed the version to 3.4.0b1dev_r75415 (and i have still this >> egg in my cache), but it disappeared from the rest of the world. >> this should never happen for released eggs, they should be >> considered read-only imho. > > +1 > > Eggs must not disappear, ever. Now that we have decided on eggs we > have to live with the implications. This is one of them.
- -1. Another implication: eggs which have '-r[0-9]+' in them should *never* be released to any location where they might be found by anyone not explicitly requesting them. Specifically, this means the cheeseshop as well as any public 'find-links' or 'index-url' location. Nobody should ever "nail" a dependency to such an egg without taking responsibility for hosting it themselves. Frankly, anybody who *wants* such an egg should instead be using a checkput + 'setup.py develop', instead; anything else is an invitation to disaster. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG8TBp+gerLs4ltQ4RAlxoAJ41h/M0PctfXgYgYm4xZu7S0RbyaACg0pS+ cxk8UG6sOYV1k+x4QZ7X29E= =zhef -----END PGP SIGNATURE----- _______________________________________________ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
