From abmanock at earthlink.net  Wed Mar 13 08:45:17 2002
From: abmanock at earthlink.net (Adam Manock)
Date: Sun Aug 10 16:46:42 2008
Subject: [Zope-Packagers] Re: Zope 2.5.0 RPMS was Re: [Zope] What causes the community
 to stall so often?
In-Reply-To: <3C8F403C.5030700@zope.com>
References: <5.1.0.14.2.20020308135605.0267c040@pop.earthlink.net>
 <3C8901C7.7050203@gmx.net>
 <5.1.0.14.2.20020308135605.0267c040@pop.earthlink.net>
 <5.1.0.14.2.20020309095704.023416b0@pop.earthlink.net>
Message-ID: <5.1.0.14.2.20020313081411.02363720@pop.earthlink.net>

Initial requirements for a Zope RPM need to be nailed down.

So far, IMHO:

Zope >= 2.5.0 requires python2.1 >= 2.1.2 enforced by RPM (reduce 
zope@zope.org list traffic :-)

Minimum of Zope data area broken out of main directory heirachy to a 
/var/zope INSTANCE_HOME.

standard chkconfig stuff, zope user creation, etc.

Undecided:

PCGI?
Put zope-PCGI in a separate spec / source package? An additional (optional 
to build and install) package?
Narrowing the scope to only support zope w/zserver in the main package 
initially = earlier initial release.

Ron, does your 2.5.0 package already take care of cleanly building PCGI??

Adam

PS <thread should continue on Zope-Packagers list, this being the first and 
last cross post :-)>

At 07:04 AM 3/13/02, Paul Everitt wrote:

>Yes, once someone feels they have the right recipe, we can add it to our 
>default build process.
>
>I propose that we take this item to the next step by peeling it out of 
>this thread, taking it over to the dormant zope-packagers list, and 
>ironing out the details:
>
>   http://lists.zope.org/mailman/listinfo/zope-packagers
>
>I'll also note that Matt Behrens has signed up for a proposal that 
>revisits the installation process, to be looked at for Zope 2.6.
>
>--Paul
>
>Adam Manock wrote:
>>At 06:59 AM 3/9/02, Dieter Maurer wrote:
>>
>>>Adam Manock writes:
>>>  > In the spirit of scratching your own itch, I have built an RPM set 
>>> for Zope
>>>  > 2.5.0 that "works on my machine" :-)
>>>Congratulations and thank!
>>>
>>>However, we know that Zope 2.5.0 contains a serious bug that may
>>>lead to memory corruption and nasty crashes. A 2.5.1 RPM would
>>>probably be more helpful.
>>
>>I built these RPMS to be simple and maintainable, it shouldn't take me 
>>long to package up 2.5.1 when it gets out of beta. Personally, I wasn't 
>>planning to deploy 2.5.0 in production, I'm planning on waiting and 
>>rolling out 2.5.1 instead. I built 2.5.0 RPMS strictly to aid in 
>>deployment of Zope to test / dev boxes. If anyone really needs a source 
>>rpm of 2.5.1b1 I'd be happy to build it for them, all you gotta do is ask :-)
>>Another kind community member is going to cast a second set of eyes over 
>>the 2.5.0 RPM, as I don't exactly trust any package that hasn't been QA'd 
>>by at least two people, even if I did build it myself ;-)
>>Eventually I'd like to see Zope Corp throw a the necessary scripts, 
>>readme and spec into the Zope source tree so that a CVS checkout of a 
>>tarball followed by a rpmbuild -ta TARBALL is all you would need to do to 
>>build new Zope rpms. Zope Corp doesn't need to maintain the stuff, 
>>although that would be nice. If the community maintainer(s) were informed 
>>of changes affecting the RPM build, like the access --> inituser change, 
>>and were in the loop about release target dates, etc, they could have 
>>rpms built in time for the release.
>>Adam
>>_______________________________________________
>>Zope maillist  -  Zope@zope.org
>>http://lists.zope.org/mailman/listinfo/zope
>>**   No cross posts or HTML encoding!  **
>>(Related lists - http://lists.zope.org/mailman/listinfo/zope-announce
>>http://lists.zope.org/mailman/listinfo/zope-dev )
>
>
>
>
>_______________________________________________
>Zope maillist  -  Zope@zope.org
>http://lists.zope.org/mailman/listinfo/zope
>**   No cross posts or HTML encoding!  **
>(Related lists - http://lists.zope.org/mailman/listinfo/zope-announce
>http://lists.zope.org/mailman/listinfo/zope-dev )



From matt at zigg.com  Wed Mar 13 08:57:54 2002
From: matt at zigg.com (Matt Behrens)
Date: Sun Aug 10 16:46:42 2008
Subject: [Zope-Packagers] Re: Zope 2.5.0 RPMS was Re: [Zope] What causes the community to stall so often?
Message-ID: <E16l9GM-0001jw-00@kiwi.nocdns.com>

Hi guys, wasn't aware anyone was listening on this list, judging from
the archives :-)  Sorry I missed the zope@ thread, I don't subscribe
anymore because the traffic level is (used to be?) a recipe for insanity.

As Paul hinted at, I'm currently working on revamping the build,
installation, and instance management processes for Zope 2.6, based on
existing work.  I have a vested interest in this because I build the
OpenBSD package, which currently installs the software home into
$PREFIX/lib/zope and includes a script to build an instance home for
you.  I want to expand on this.

I don't know what your timetables are, but if you're in the process of
rethinking this, wait till the weekend is past, I should have something
by then.  What I do come up with will most likely be able to be used
with 2.4 and 2.5. and it'll mean you don't have to do it again for 2.6. :-)


From matt at zigg.com  Wed Mar 13 08:58:00 2002
From: matt at zigg.com (Matt Behrens)
Date: Sun Aug 10 16:46:42 2008
Subject: [Zope-Packagers] Re: Zope 2.5.0 RPMS was Re: [Zope] What causes the community to stall so often?
Message-ID: <E16l9GS-0001k9-00@kiwi.nocdns.com>

Hi guys, wasn't aware anyone was listening on this list, judging from
the archives :-)  Sorry I missed the zope@ thread, I don't subscribe
anymore because the traffic level is (used to be?) a recipe for insanity.

As Paul hinted at, I'm currently working on revamping the build,
installation, and instance management processes for Zope 2.6, based on
existing work.  I have a vested interest in this because I build the
OpenBSD package, which currently installs the software home into
$PREFIX/lib/zope and includes a script to build an instance home for
you.  I want to expand on this.

I don't know what your timetables are, but if you're in the process of
rethinking this, wait till the weekend is past, I should have something
by then.  What I do come up with will most likely be able to be used
with 2.4 and 2.5. and it'll mean you don't have to do it again for 2.6. :-)


From paul at zope.com  Wed Mar 13 10:11:11 2002
From: paul at zope.com (Paul Everitt)
Date: Sun Aug 10 16:46:42 2008
Subject: [Zope-Packagers] DISCUSS: Making RPMs
References: <5.1.0.14.2.20020308135605.0267c040@pop.earthlink.net> <3C8901C7.7050203@gmx.net> <5.1.0.14.2.20020308135605.0267c040@pop.earthlink.net> <5.1.0.14.2.20020309095704.023416b0@pop.earthlink.net> <5.1.0.14.2.20020313081411.02363720@pop.earthlink.net>
Message-ID: <3C8F6C0F.1070506@zope.com>

Adam Manock wrote:
> Initial requirements for a Zope RPM need to be nailed down.
> 
> So far, IMHO:
> 
> Zope >= 2.5.0 requires python2.1 >= 2.1.2 enforced by RPM (reduce 
> zope@zope.org list traffic :-)


... and I'm changing the stinking subject line.  Whew!

As Matt noted, he's working on an official proposal that sketches out an 
overhaul of the installation process.  I think we can keep discussing 
RPM-specific matters until we hear back from him.  For now, I'll try to 
respond to these points.

> Minimum of Zope data area broken out of main directory heirachy to a 
> /var/zope INSTANCE_HOME.

I think Matt will give us an answer here...

> standard chkconfig stuff, zope user creation, etc.
> 
> Undecided:
> 
> PCGI?
> Put zope-PCGI in a separate spec / source package? An additional 
> (optional to build and install) package?

I think it is reasonable to hide pcgi.  We *certainly* don't need it on 
by default.

> Narrowing the scope to only support zope w/zserver in the main package 
> initially = earlier initial release.

Right.

I have long thought that we should migrate binary stuff into a separate 
package.  Alternatively, have a zope-base that contains the minimum 
necessary, including C extensions.  This makes applying updates 
smaller/easier.

In the future, we might use this base package to get Python packages 
from a CPAN-like service (e.g. Kapil's) and Zope packages from a similar 
service.

--Paul



From raarts at netland.nl  Wed Mar 13 11:26:00 2002
From: raarts at netland.nl (Ron Arts)
Date: Sun Aug 10 16:46:42 2008
Subject: [Zope-Packagers] subscribe
Message-ID: <3C8F7D98.3040307@netland.nl>


-- 
Netland Internet Services
bedrijfsmatige internetoplossingen

http://www.netland.nl   Kruislaan 419              1098 VA Amsterdam
info: 020-5628282       servicedesk: 020-5628280   fax: 020-5628281
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3276 bytes
Desc: S/MIME Cryptographic Signature
Url : http://mail.zope.org/pipermail/zope-packagers/attachments/20020313/42f5f876/smime.bin
From matt at zigg.com  Fri Mar 15 08:14:32 2002
From: matt at zigg.com (Matt Behrens)
Date: Sun Aug 10 16:46:42 2008
Subject: [Zope-Packagers] InstallationAndConfiguration proposal
Message-ID: <E16lrXU-000664-00@kiwi.nocdns.com>

The proposal previously alluded to is available at
http://dev.zope.org/Wikis/DevSite/Proposals/InstallationAndConfiguration.

I think at this point the plan is that this will only go into the head
(and that might not even be the case, we'll see how it goes); but I will
at least be making a patchset for 2.5, since I would like to adopt this
for the OpenBSD package.


From raarts at netland.nl  Mon Mar 18 15:28:05 2002
From: raarts at netland.nl (Ron Arts)
Date: Sun Aug 10 16:46:42 2008
Subject: [Zope-Packagers] Installation Proposal
Message-ID: <3C964DD5.6080003@netland.nl>

I'm sorry, I am a Zope newbie, even structured text is new to me,
so my comments on the proposal are a bit messed up, and I can't find
a way to edit them.

Anyway, I created some Zope and product RPM's and I'd like to put some
on zope.org. Someone mentioned I needed to get more upload rights,
I should send a message to zope-web is that @zope.org?

Ron.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3291 bytes
Desc: S/MIME Cryptographic Signature
Url : http://mail.zope.org/pipermail/zope-packagers/attachments/20020318/7a1fb079/smime.bin