https://bugzilla.rpmfusion.org/show_bug.cgi?id=4393
--- Comment #25 from Andrew Bauer <zonexpertconsulting(a)outlook.com> ---
Greetings Xavier,
Thank you for the prodding me. Following up here has been in the back of mind
for a couple weeks now.
With the help of Damian, all of ZoneMinder's dependencies are now in the Fedora
& EPEL repos. This has been a great learning experience.
Just to be sure we are set, I did a mock build against el6, el7, f24, and f25
this morning, using the appropriate rpmfusion mock config, and they all built
successfully.
This is the spec file to use to build our latest 1.30.2 release:
https://raw.githubusercontent.com/ZoneMinder/ZoneMinder/1.30.2/distros/re...
However, this is not the most recent. I've already made changes, which will
appear in the upcoming 1.30.3 release "soon". You can see the progress of that
specfile in our master branch here:
https://raw.githubusercontent.com/ZoneMinder/ZoneMinder/master/distros/re...
In the grand scheme of things, I'm trying to manage a single zoneminder spec
file for three related, but different, purposes:
- rpmfusion
- an upstream build system for nightly builds
- experimental nginx support
This is the underlying reason why one might see content in the spec file that,
today, might not apply to rpmfusion.
During the process, I have indeed become part of the Fedora packaging group, so
if I understand correctly that means I don't need an rpmfusion sponsor, but
don't I still need someone to add my FAS account to the rpmfusion packaging
group? My fas account name is Kni.
In any case, feel free to continue the review process when your time allows.
Due to the complicated nature of the zoneminder specfile, I'm sure there might
be additional questions or concerns.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.