New Zenoss RPMs
Christopher Blunck
chris at zenoss.com
Fri Feb 29 04:38:03 UTC 2008
We're extremely interested in making it into EPEL. The biggest hurdle
we face right now is not a technical one; it's a policy/procedure
problem. Simply put: we (or more specifically I) am unfamiliar with
the EPEL/Fedora/RHEL policies and procedures that are used to qualify
a project to be included into your baseline.
I'm trying to make sure that we conform to your policies and
procedures, and that we follow all of the guidelines the community
offers as criteria for inclusion into the repository. Sometimes those
policies conflict with our existing build system (e.g. the situation
with python 2.4). When that comes up we (I) try to re-engineer our
build-system to accommodate your criteria because honestly your
procedures are usually best practices. :)
Tomorrow I'm going to submit our .spec and .src.rpm for review. I
expect that as a result of that submission we'll have an opportunity
to work through some more of details associated with being included
into the repository.
Thanks guys for all your help! Please give us a chance - we're just
trying to understand what we need to do to be included in your repo! :)
-c
On Feb 28, 2008, at 10:14 PM, Mike McGrath wrote:
> On Thu, 28 Feb 2008, Christopher Blunck wrote:
>
>> On Feb 28, 2008, at 4:26 PM, Rahul Sundaram wrote:
>>
>>> Christopher Blunck wrote:
>>> Assuming you are interested in maintaining the software package on a
>>> continuous basis within EPEL, refer
>>>
>>> http://fedoraproject.org/wiki/EPEL/FAQ#head-0ea98f661aff25e65d3781c334473985a0e65f55
>>
>> The Zenoss Dev Team will be responsible for maintaining the
>> software package.
>> They will most likely ask me to be the individual responsible for
>> doing the
>> work, but as a collective we will make sure that it is maintained
>> on a
>> continuous basis.
>>
>>
>
> To be clear, I suspect many people are interested in getting this
> package
> into epel. Please let us know if you have any questions or concerns
> (like
> missing deps for example)
>
> -Mike
>
> _______________________________________________
> epel-devel-list mailing list
> epel-devel-list at redhat.com
> https://www.redhat.com/mailman/listinfo/epel-devel-list
More information about the epel-devel-list
mailing list