[Zope3-dev] eggs for Zope 3 extensions

2006-04-04 Thread Martijn Faassen

Hi there,

I know there are lots of ideas about eggs in Zope 3 land, so I'd like to 
pick the brains of the people who have looked into this more than I have 
for a bit.


First to say what I'm not talking about: I'm not talking about eggifying 
Zope 3 itself. This is a valuable project but hopefully mostly 
independent of what I'd like to do.


There are a whole bunch of interesting Zope 3 extensions that I'd like 
to use in a project, such as some of the various zc.* packages. Imagine 
they've been turned into eggs. Now my project wants to use them. What's 
the Zope 3 pattern for this, if any? The project needs to have some way 
to do the following:


svn co myproject
cd myproject
make

where 'make' creates a Zope 3 installation, and downloads all the eggs 
listed as requirements for this project from the net, and installs them 
so that the Zope 3 instance actually picks them up.


In particular, are there any ideas of how the -configure.zcml and 
-meta.zcml files would end up being generated and installed in 
package-includes? Eggs do not provide for this directly, but perhaps 
there are some ideas about Zope 3 specific eggs that do?


Regards,

Martijn
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com



Re: [Zope3-dev] eggs for Zope 3 extensions

2006-04-04 Thread Sidnei da Silva
On Tue, Apr 04, 2006 at 02:51:37PM +0200, Martijn Faassen wrote:
| where 'make' creates a Zope 3 installation, and downloads all the eggs 
| listed as requirements for this project from the net, and installs them 
| so that the Zope 3 instance actually picks them up.

I think you would give a argument to easy_install to install the eggs
in `INSTANCE_HOME/lib/python`.

| In particular, are there any ideas of how the -configure.zcml and 
| -meta.zcml files would end up being generated and installed in 
| package-includes? Eggs do not provide for this directly, but perhaps 
| there are some ideas about Zope 3 specific eggs that do?

I think those would be handled by 'entry points'.

-- 
Sidnei da Silva
Enfold Systems, Inc.
http://enfoldsystems.com
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com



Re: [Zope3-dev] eggs for Zope 3 extensions

2006-04-04 Thread Martijn Faassen

Sidnei da Silva wrote:

On Tue, Apr 04, 2006 at 02:51:37PM +0200, Martijn Faassen wrote:
| where 'make' creates a Zope 3 installation, and downloads all the eggs 
| listed as requirements for this project from the net, and installs them 
| so that the Zope 3 instance actually picks them up.


I think you would give a argument to easy_install to install the eggs
in `INSTANCE_HOME/lib/python`.


Right, I can make it work, I just wondered if there was some canonical 
way. :)


| In particular, are there any ideas of how the -configure.zcml and 
| -meta.zcml files would end up being generated and installed in 
| package-includes? Eggs do not provide for this directly, but perhaps 
| there are some ideas about Zope 3 specific eggs that do?


I think those would be handled by 'entry points'.


Looking them up... As far as I understand them, Zope 3 would need to be 
able to understand entry points before I could use these in a project 
that uses Zope 3, right?


Regards,

Martijn


___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com



Re: [Zope3-dev] eggs for Zope 3 extensions

2006-04-04 Thread Fred Drake
On 4/4/06, Martijn Faassen [EMAIL PROTECTED] wrote:
 Another question about eggs: I assume that Zope 3 extensions at present
 cannot be zipped, as Zope needs access to their zcml files. Correct?

Extensions that contain ZCML or other file-based resources (page
templates, ZConfig schema components) cannot currently be used
directly from a ZIP file.

I started work to support that on the zipimport-branch, but didn't
have time to finish the proposal that went with that.  That branch
allowed ZCML and page templates to be loaded from within ZIP files,
and support code to allow packages to refer to their own resources
abstractly, even without the egg-support code being available.  The
changes on that branch work with ZIP-based imports generally, and are
not specific to eggs (but I think they work fine with eggs).

There's a wiki page about this at

http://dev.zope.org/Zope3/ZIPImportSupportForZope3


  -Fred

--
Fred L. Drake, Jr.fdrake at gmail.com
Don't let schooling interfere with your education. -- Mark Twain
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com