[Zope-dev] Packaging Zope for Fedora

[Andreas Jung]

Hi,

speaking as the Zope 2 release manager: I am strongly opposed against 
splitting Zope
yourself into different packages and modules. With Zope 2 depending from 
various Zope 3 packages (roughly 80-90) we have already the situation to 
keep track which packages belong together. This will become even more 
complicated when each Zope 3 package will have its own life-cycle.
I doubt that you as a package can keep track in a reliable way with those
requirements. It is somewhat hard for me to follow. So why can't you leave 
the Zope source packages as they are? Splitting up Zope into even more 
packages is even more error-prone.  Re-packaged Zope distributions always 
raised more problems in the past than they really solved. The deployment 
for Zope-based applications is nowadays based on zc.buildout. Serious 
solutions providers never go with distribution-specific packages.

Andreas



--On 21. März 2008 11:57:31 -0700 Timothy Selivanow 
<timothy.selivanow at virtualxistenz.com> wrote:

> As the subject implies, I'm working on a package for Fedora.  I've come
> across some missing dependencies, and some that are different versions.
> Because of the way that Python packages are put together (shared library
> environment), I'm trying to strip out everything that is not Zope
> specific (e.g. mechanize, docutils, etc.) that way Zope won't clobber
> already existing packages, and new packages won't clobber Zope.
>
> Here is my list (that I've discovered so far...) and some notes and
> questions.  I would appreciate any information on resolving these.  My
> list was taken from Zope-3.4.0c1/build/lib.linux-x86_64-2.5 (in my arch
> specific case...) after doing a `python install.py build` (side note,
> why is it called install.py and not setup.py?).
>
> BTrees --
> 	Does not currently exist in Fedora as a separate package.
> 	Is this of Zope origin? (If not, where? Required version?)
> 	If Zope origin, is it useful outside of Zope?
> 	
> ClientForm --
> 	This currently exists in Fedora (version 0.2.7)
> 	Diffing the directories and files reveals differences.
> 	What version is required for Zope? What about newer versions?
>
> twisted --
> 	This currently exists in Fedora (version 2.4.0)
> 	Diffing the directories reveals that is it mostly compatible,
> 		however, missing some features (I have a list).
> 	What parts are required by Zope?
> 	Some of the missing parts are no longer being maintained, or are
> 		incompatible with newest Twisted (2.5.0). Thoughts?
>
> mechanize --
> 	This currently exists in Fedora (version 0.1.6)
> 	Diffing the directories and files reveals differences.
> 	What version is required for Zope? What about newer versions?
>
> persistent --
> 	Does not currently exist in Fedora as a separate package.
> 	Is this of Zope origin? (If not, where? Required version?)
> 	If Zope origin, is it useful outside of Zope?
>
> pytz --
> 	This currently exists in Fedora (version 2006p)
> 	Diffing the directories and files reveals differences.
> 	What version is required for Zope? What about newer versions?
> 	The Zope versions do not have the .py extension.  Possible
> 		problems with Zope if they do (i.e., lib resolving)?
>
> RestrictedPython --
> 	Does not currently exist in Fedora as a separate package.
> 	Is this it? <http://pypi.python.org/pypi/RestrictedPython/3.4.2>
> 	Required version for Zope? What about newer versions?
>
> ThreadedAsync --
> 	Does not currently exist in Fedora as a separate package.
> 	Is this of Zope origin? (If not, where? Required version?)
> 	If Zope origin, is it useful outside of Zope?
>
> transaction --
> 	Does not currently exist in Fedora as a separate package.
> 	Is this of Zope origin? (If not, where? Required version?)
> 	If not Zope origin, is it useful outside of Zope?
>
>
> Also, there is an existing package in Fedora called
> python-zope-interface, version 3.0.1 I assume (in F8), and I'm wondering
> if it would be worth keeping separate (or at least available, updated,
> maybe with a Conflicts: zope) in Fedora and are there other parts of
> Zope (e.g. ZODB, ZEO) that would be useful by themselves?
>
> I'm sorry if this seems daunting (it is on my side ;) and/or demanding,
> but I would like this packaged the best possible way for both projects.
> Who knows, this might show up in future RHEL versions (maybe I'm
> delusional ;)
>
>
> Thank you for your time and patience.
>
> --Tim
>  ________________________________________________________________________
> _  / According to Kentucky state law, every person must take a bath at
> least \ \ once a year.
> /
>  ------------------------------------------------------------------------
> -    \
>    \   \
>         \ /\
>         ( )
>       .( o ).
>
> _______________________________________________
> Zope-Dev maillist  -  Zope-Dev at zope.org
> http://mail.zope.org/mailman/listinfo/zope-dev
> **  No cross posts or HTML encoding!  **
> (Related lists -
>  http://mail.zope.org/mailman/listinfo/zope-announce
>  http://mail.zope.org/mailman/listinfo/zope )



-- 
ZOPYX Ltd. & Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany
Web: www.zopyx.com - Email: info at zopyx.com - Phone +49 - 7071 - 793376
Registergericht: Amtsgericht Stuttgart, Handelsregister A 381535
Geschäftsführer/Gesellschafter: ZOPYX Limited, Birmingham, UK
------------------------------------------------------------------------
E-Publishing, Python, Zope & Plone development, Consulting
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
Url : http://mail.zope.org/pipermail/zope-dev/attachments/20080321/d4d9f2fb/attachment-0001.bin