Zenoss Core

[Christopher Blunck]

Hello all,

I work on the Zenoss project and we're interested in figuring out how  
to get our "Zenoss Core" product into the Fedora 8 repositories so  
that end-users can install us via a simple "yum install zenoss".  I  
sent a few private emails to Warren Tagomi to talk about what we had  
to do to be included in Fedora's repositories.

The gist of that conversation was that we would not qualify for  
inclusion due to our dependence on Zope 2.x, which requires Python  
2.4.  Our solution to that problem under Fedora (as well as on other  
distributions) has been to ship our own python installation with our  
product.  Python 2.4 is installed under /opt/zenoss.

Warren suggested I look into the livna repository, and I created a  
ticket there that asks that we are included in their repository:
   http://bugzilla.livna.org/show_bug.cgi?id=1817

After several comments it seems like the consensus is for us to use  
the compat-python24 package rather than ship our own version of  
python.  We're working on that from an engineering standpoint.

Thorsten Leemhius suggested we consider the EPEL repository since it  
feeds RHEL.  I replied saying that we're in RHX already (but not for  
Zenoss Core).

I wanted to join this list to get a better idea for where we can park  
our OSS "Zenoss Core" product such that it is included in subsequent  
Fedora releases, is considered for inclusion in upcoming RHEL  
releases, and is possibly also included in RHX (alongside our  
commercial enterprise product).  I'm very new to the EPEL/Livna/Fedora  
repository landscape, but I'm very familiar with Linux, distros, yum,  
up2date, and all the other infrastructure.  I'm asking for a bit of  
help in understanding what repositories and processes feed  
distributions and releases so that I can understand where we should  
try to park our OSS "Zenoss Core" product.

Any insight (wikis/FAQs/HOWTOs) that anyone can provide would be  
happily accepted! :)


-c

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/epel-devel-list/attachments/20080118/bd53db4f/attachment.htm>