On Tue, Aug 4, 2015 at 12:55 AM, Mikolaj Izdebski <mizdebsk(a)redhat.com>
wrote:
On 08/03/2015 09:05 PM, Dave Johansen wrote:
> On Thu, Jul 30, 2015 at 2:54 PM, Mikolaj Izdebski <mizdebsk(a)redhat.com>
> wrote:
>> I'm affraid there is no easy way of getting all transitive
>> bulid-requires... When I have some free time I can try to write a script
>> to come up with list of packages that would need to be built for EPEL 7.
>> I wouldn't be surprised if it was around 50 packages.
>>
>
> I did a yum install of the BuildRequires and here's the list of packages
> that it says weren't available:
[...]
>
> That's 69 packages, so here's my questions:
> In general, how much work will it be for each of the packages?
> Would I have to be the maintainer for all of them?
It's probably less than that - one package usually has multipse mvn(*)
provides. But then there will be other packages - transitive requires
and build-requires. And yes, you would need to become maintainer of all
required packages.
Sadly, I'm just not up for maintaining >10 packages that I know nothing
about and have no direct use for. So it sounds like packing Jenkins for
EPEL won't be something that I'll pursue.
I just realised that Michal Srb is working on packaging Jenkins as
software collection for RHEL 6 and 7. The results are available on [1].
This work is not complete yet, but I assume all packages listed there
will need to be built for EPEL 7 if you want to have jenkins there.
[1]
https://copr-fe.cloud.fedoraproject.org/coprs/msrb/jenkins1609/monitor/
This is interesting and I'll definitely look into, but right now it sounds
like just using the .rpm files that are released by Jenkins is the way that
we'll go.
Thanks,
Dave