On 10/7/06, Jim Fulton <[EMAIL PROTECTED]> wrote:
Baiju M wrote:
> Hi,
>    Can I commit zope.deferredimport to the toplevel of svn,
> like zope.interface,zope.proxy etc.

That would be great.


 Will you also release an egg to pypi? :)

Done. Also added 'J1m' as owner.

> I have added README.txt, setup.py, test.py etc. see this:
> http://zissue.berlios.de/z3/zope.deferredimport.tar.bz2
> Please confirm these steps:
> $ svn mkdir svn+ssh://[EMAIL PROTECTED]/repos/main/zope.deferredimport
> $ svn co svn+ssh://[EMAIL PROTECTED]/repos/main/zope.deferredimport
> $ cd zope.deferredimport
> $ mkdir trunk
> $ mkdir branches
> $ mkdir tags
> $ svn add trunk branches tags

Minor note: I typically set up the full tree in the original
transaction that sets up the project.  You can give multiple directories
on the mkdir line.  I have a script named "z" that echos the repo url, so
I'd do:

   svn mkdir `z`/zope.deferredimport `z`/zope.deferredimport/trunk 
`z`/zope.deferredimport/branches `z`/zope.deferredimport/tags

Thanks, I used this trick :)

> $ cd trunk
> (Now add package here,
> then set svn:external to (in src/zope)
>  deferredimport
> svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/deferredimport
> Also set svn:ignore in / and src/)

It would be nice to also turn it into a buildout so that you could run it's
tests in a project checkout.  See for example:


First I will learn zc.buildout, then I will try.

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

Reply via email to