Re: Re: zope.dottedname doesn't have a CHANGES.txt (again?)

"Lennart Regebro" <[email protected]> Wed, 3 Oct 2007 19:43:55 +0200
Newsgroups gmane.comp.web.zope.zope3
Message-ID <[email protected]>
On 10/3/07, Fred Drake <[email protected]> wrote:
> On 10/3/07, Lennart Regebro <[email protected]> wrote:
> > It currently only makes releases as tgz, but adding eggs should be so
> > hard (it's done by calling setup.py anyway if I remember correctly).
>
> tgz files are all that's needed (or wanted); there's no reason to use
> a .egg file.  For packages that include extension modules, there are
> well-understood reasons to stick with a source distribution.

Oh, well then maybe we don't need egg support. That's good.

However, I also just realizd that bundleman currently uses the pattern
of having a CHANGES file, and a HISTORY file and a VERSION file, and
then massaging them and renaming them to CHANGES.txt HISTORY.txt and
version.txt when used, and I think we still would need some change to
support calling the files CHANGES.txt directly, or updating all the
eggs might be a bit much work. (Unless we make a script for that).

But it is a very good tool for making releases. It also has this nice
support for releasing all the products in a whole svn-bundle, if they
need releasing, which is very nice.

-- 
Lennart Regebro: Zope and Plone consulting.
http://www.colliberty.com/
+33 661 58 14 64