On Friday 09 November 2007, Lennart Regebro wrote: > On Nov 9, 2007 4:34 PM, Philipp von Weitershausen > > <[EMAIL PROTECTED]> wrote: > > Those are exactly the problems with the locked down index: > > > > * You can always use *more* packages but you'll have to lock them down > > yourself, can't use another KGS for those > > Could we create a grok KGS which is generated by a python-script, that > takes the correct zope3 KGS as a base?
Based on my son's behavior today, you will be able to do this in a few hours. > > * You cannot say "I know the KGS prefers zope.frobnaz 1.2.3, but I > > deliberately want to upgrade to zope.frobnaz 2.0.2". It won't work > > because the index simply doesn't expose the 2.0.2 version of > > zope.frobnaz. With the extends/bases behavior I am planning to add, you will be able to do exactly this. > This needs to be fixed in setup tools some time in the future, then, > because it will severly limit the usablility of a KGSs if you can't > use this. You very often need to upgrade one package... I think that with a little bit more code for the KGS and considering all the other possibilities, such as find-links and versions, we have enough flexibility. I think the challenge will be to come up with a recommended way to do all these things. Maybe we should collect our use cases again and see how they can be solved. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training _______________________________________________ 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 )