Re: [Zope3-Users] Re: Known-good-sets problem

2007-10-06 Thread Jim Fulton


On Oct 6, 2007, at 5:28 AM, Martijn Faassen wrote:


Benji York wrote:

Stephan Richter wrote:
2. How many packages should be controlled in this index? I think  
we should definitely add packages from z3c and the zc namespace.
What is the motivation to include non-controlled packages?  I  
suppose it is to let people use those packages with (in this case)  
Zope 3.4.  What if someone wants Zope 3.4 and Twisted version X  
and Plone version Y (just making those up).  Perhaps we need a way  
to refer to several KGS when constructing an application.  Or is  
one KGS supposed to define a "universe" of packages known to work  
together.  If so, I would think there would be no place for non- 
controlled packages.


A feature to combine lists of versions is definitely needed. I may  
be a developer of an application that uses both Grok and KSS, for  
instance. This can be solved by me maintaining my own list, but I'd  
prefer to rely on two lists that are already there.


That's the application developer's case. The framework developer's  
case requires me to publish such combined lists. If I have my own  
framework on top of Grok and KSS, I'd like to publish a list that's  
a combination of those without having to copy them.


As I mentioned in my response to Benji, it's tricky to get the  
semantics right.  IMO, you want a particular KGS to be  
authoritative.  There isn't anything in setuptools to support this  
semantic.  You can use the mirroring approach (maybe with some minor  
tweaking) to combine KGSs on the server.


Jim

--
Jim Fulton
Zope Corporation


___
Zope3-users mailing list
Zope3-users@zope.org
http://mail.zope.org/mailman/listinfo/zope3-users


[Zope3-Users] Re: [Zope3-dev] Known-good-sets problem

2007-10-06 Thread Jim Fulton


On Oct 5, 2007, at 10:45 PM, Benji York wrote:


Stephan Richter wrote:
2. How many packages should be controlled in this index? I think  
we should definitely add packages from z3c and the zc namespace.


What is the motivation to include non-controlled packages?  I  
suppose it is to let people use those packages with (in this case)  
Zope 3.4.


Yes

  What if someone wants Zope 3.4 and Twisted version X and Plone  
version Y (just making those up).


That's why the KGS index is a PyPI mirror of all uncontrolled packages.

  Perhaps we need a way to refer to several KGS when constructing  
an application. Or is one KGS supposed to define a "universe" of  
packages known to work together.  If so, I would think there would  
be no place for non-controlled packages.


The semantics I think we want are kind of tricky. A KGS index needs  
to be authoritative for the projects it controls.  If we looked in  
multiple KGSs, there would need to be semantics for deciding which  
was authoritative.  setuptools lets you define a single index and  
multiple find-link servers.  The highest version found on any server  
is authoritative.  I think supporting multiple KGSs with the right  
semantics would be useful, but there isn't a way to do it in  
setuptools. We can achieve the  same effect on the server.  For  
example, with this software, you could chain several KGSs together.


Jim

--
Jim Fulton
Zope Corporation


___
Zope3-users mailing list
Zope3-users@zope.org
http://mail.zope.org/mailman/listinfo/zope3-users


[Zope3-Users] Re: Known-good-sets problem

2007-10-06 Thread Martijn Faassen

Benji York wrote:

Stephan Richter wrote:
2. How many packages should be controlled in this index? I think we 
should definitely add packages from z3c and the zc namespace.


What is the motivation to include non-controlled packages?  I suppose it 
is to let people use those packages with (in this case) Zope 3.4.  What 
if someone wants Zope 3.4 and Twisted version X and Plone version Y 
(just making those up).  Perhaps we need a way to refer to several KGS 
when constructing an application.  Or is one KGS supposed to define a 
"universe" of packages known to work together.  If so, I would think 
there would be no place for non-controlled packages.


A feature to combine lists of versions is definitely needed. I may be a 
developer of an application that uses both Grok and KSS, for instance. 
This can be solved by me maintaining my own list, but I'd prefer to rely 
on two lists that are already there.


That's the application developer's case. The framework developer's case 
requires me to publish such combined lists. If I have my own framework 
on top of Grok and KSS, I'd like to publish a list that's a combination 
of those without having to copy them.


Regards,

Martijn

___
Zope3-users mailing list
Zope3-users@zope.org
http://mail.zope.org/mailman/listinfo/zope3-users