-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Chris Withers wrote:
> Dieter Maurer wrote:
>> Tres has earlier proposed a meta egg to represent "versions.cfg" in
>> a setuptools only (non buildout) environment.
>>
>> A meta egg is an egg that only list dependencies and does not contain
>> code of its own.
> 
> Indeed, so we'd need 2 eggs for Zope 2 :-(
> 
> Something I bumped into recently:
> 
> If the Zope 2 egg actually hard-specifies its dependencies, how do I 
> upgrade any of those dependencies to newer versions that fix bugs i may 
> have encountered/fixed?

You roll another version of the meta-egg with updated dependencies (the
meta-egg takes the place of the KGS).  This isn't any harder than
updating the buildout.cfg / versions.cfg, assuming you maintain the
meta-egg which corresponds to your needs in SVN someplace.


Tres.
- --
===================================================================
Tres Seaver          +1 540-429-0999          tsea...@palladion.com
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

iD8DBQFJ4NJI+gerLs4ltQ4RAmYWAKCW2rH0QnP5eLB3gEigZ0aFN53y8ACgkV1q
vaUreNgVdJj1kdjCwQQxv/M=
=DAcs
-----END PGP SIGNATURE-----

_______________________________________________
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )

Reply via email to