Get rid of configure/make? (was Re: [Zope-dev] Re: SVN: Zope/trunk/ Merge philikon-zope32-integration branch. Basically, this branch entails:)

[Morten W. Petersen]

> I wasn't arguing that configure/make was hard to use.  I'm arguing
> that it's something extra to maintain and is just silly.
> 
> It's main benefit is that it leverages a familiar pattern, but
> I'm not convinced that it's worth it. Also, as tools like rpm and
> deb become more widely used, I'm not sure how familar the configure/make
> dance is.  Other than Python and Zope, I never use configure/make anymore.

My experience is that .rpm and .deb packages are poorly maintained, so
if someone is serious about using Zope and related products, downloading
and installing from source is the only way to go.

We also have tools internally that depend on the configure/make dance,
and I'm sure others who put up a lot of Zope instances do as well..  :)

-Morten
-------------- next part --------------
A non-text attachment was scrubbed...
Name: morten.vcf
Type: text/x-vcard
Size: 290 bytes
Desc: not available
Url : http://mail.zope.org/pipermail/zope-dev/attachments/20051105/61348d6f/morten.vcf