Hi,

In message <17711.41471.436403.191741@viola.nmsu.edu>
	on Fri, 13 Oct 2006 08:26:07 -0600,
	Brook Milligan <brook@biology.nmsu.edu> wrote:
> What is the next step?  Should there be a greater consensus that this
> is reasonable?  Should the ideas be fleshed out further or are they
> sufficiently detailed to be useful?  For example, does there need to
> be some discussion of how the dependencies are recorded in variables
> like ZOPE_VERSION_REQUIRED?  Is that a list of discrete versions?  Is
> it a dewey-type range?  Finally, is anyone able to implement some of
> this?
Here is just FYI.  I've slowly implement zope packages:

% ls -d /var/db/pkg/zope* 
/var/db/pkg/zope210-2.10.3/
/var/db/pkg/zope29-2.9.7/
/var/db/pkg/zope29-ejSplitter-0.5.1/
/var/db/pkg/zope29-jaMailHost-0.4.4/
/var/db/pkg/zope29-plone25-2.5.2/
/var/db/pkg/zope29-plone25-CacheFu-2.5.2/

Related files are:
pkgsrc/www/zope/zopeversion.mk
pkgsrc/www/zope/product.mk
pkgsrc/www/zope29/ (updated)
pkgsrc/www/zope210/
pkgsrc/www/zope-ejsplitter/
pkgsrc/www/zope-jamailhost/
pkgsrc/www/plone/ploneversion.mk
pkgsrc/www/plone25/ ...
pkgsrc/www/plone25-CacheFu/ ...

Zope3 is another beast which uses "package" instead of "product".

-- 
Takahiro Kambe <taca@back-street.net>