[Zenoss-dev] Re: FC8 RPMs

[Christopher Blunck]

We actually started shipping our own Python (2.4.4) inside our RPM.   
It installs into /opt/zenoss and all of our software uses it.

We're striving towards reducing OS dependencies (like the system  
version of python and incompatibilities it presents with libs we rely  
on) as much as possible.


-c

On Jan 11, 2008, at 10:12 PM, Warren Togami wrote:

> Christopher Blunck wrote:
>> Hi Warren,
>> Mark Turner mentioned that you and he spoke last evening at a LUG  
>> down in the Triangle area.  I wanted to introduce myself as a  
>> Zenoss developer who has spent pretty considerable time working on  
>> the RPM packaging of our product.
>> Right now I'm in the process of assembling and testing a FC8 RPM  
>> (both i386 and x86_64).  Things are looking good from a build  
>> standpoint, but I can't test yet as I'm waiting for an agonizing  
>> 623 packages to be updated by yum over our network connection.
>> If you are interested in doing some pre-release testing of the RPM  
>> I'd be happy to provide you with an i386 or x86_64 binary to bang  
>> against.
>> -c
>
> Well, one key problem that will likely block entry of zenoss in  
> Fedora 8 is zope.  zope currently cannot work with python-2.5 of  
> Fedora 7 and 8.  Until zope upstream fixes this problem, it cannot  
> be supported on Fedora.
>
> http://fedoraproject.org/wiki/EPEL
> You might want to target your initial zenoss RPM packages for EPEL  
> for RHEL5.  RHEL5 has python-2.4, and EPEL has the same package  
> review guidelines and requirements for addition as the Fedora Project.
>
> If your official RPMS are living in EPEL and are well maintained,  
> they will likely be easily suitable with minor modifications for  
> Fedora in the future after upstream zope fixes their python-2.5+  
> problem.
>
> http://fedoraproject.org/wiki/Packaging/Guidelines
> Just to be clear, in order to have official packages in Fedora or  
> EPEL someone must not only follow the packaging guidelines, but also  
> maintain the package in the distribution after inclusion.  This  
> could be either someone from your company, volunteers in your  
> community, or a combination of both.
>
> Cheers,
> Warren Togami
> wtogami at redhat.com