Re: [Zope3-dev] Re: [Checkins] SVN: zc.resourcelibrary/trunk/ A basic makefile, the ZPL and copyright headers.

2006-06-15 Thread Florian Lindner
Am Donnerstag, 15. Juni 2006 04:23 schrieb Benji York: Brian Sutherland wrote: Log message for revision 68639: A basic makefile, the ZPL and copyright headers. Is there consensus about adding makefiles like this (diff below)? I personally don't like the idea, but I wanted to bring it up

Re: [Zope3-dev] Re: [Checkins] SVN: zc.resourcelibrary/trunk/ A basic makefile, the ZPL and copyright headers.

2006-06-15 Thread Brian Sutherland
On Wed, Jun 14, 2006 at 10:23:30PM -0400, Benji York wrote: Brian Sutherland wrote: Log message for revision 68639: A basic makefile, the ZPL and copyright headers. Is there consensus about adding makefiles like this (diff below)? I personally don't like the idea, but I wanted to

Re: [Zope3-dev] Re: [Checkins] SVN: zc.resourcelibrary/trunk/ A basic makefile, the ZPL and copyright headers.

2006-06-15 Thread Benji York
Brian Sutherland wrote: The reason I put them there in the first place is to nudge committers to create both the tarball and egg (for perhaps more than one python version) when creating a new release. I would prefer that be addressed outside of the source repository. Perhaps Stephan's Zope

Re: [Zope3-dev] Re: [Checkins] SVN: zc.resourcelibrary/trunk/ A basic makefile, the ZPL and copyright headers.

2006-06-15 Thread Fred Drake
On 6/15/06, Benji York [EMAIL PROTECTED] wrote: There seems to be a consensus (although not an overpowering one) that they be removed. I'll add in my +1 for removal as well, it that helps. :-) -Fred -- Fred L. Drake, Jr.fdrake at gmail.com Every sin is the result of a collaboration.

Re: [Zope3-dev] Re: [Checkins] SVN: zc.resourcelibrary/trunk/ A basic makefile, the ZPL and copyright headers.

2006-06-15 Thread Brian Sutherland
On Thu, Jun 15, 2006 at 01:32:47PM -0400, Benji York wrote: Brian Sutherland wrote: The reason I put them there in the first place is to nudge committers to create both the tarball and egg (for perhaps more than one python version) when creating a new release. I would prefer that be