https://bugzilla.redhat.com/show_bug.cgi?id=1069988 Sven Nierlein <sven@xxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sven@xxxxxxxxx --- Comment #10 from Sven Nierlein <sven@xxxxxxxxx> --- Some updates... As thruk developer and naemon core dev like Dan i hopefully can help to change things to fit the fedora requirements. 1. Dan has to look at this 2. Dan has to look at this 3. Fixed upstream 4. can't find that upstream anymore, so i assume its fixed. 5. Fixed upstream 6. This would be the package name of the standalone gui. Its not a official fedora package atm. It can go if it violates any packaging guidelines. 7. this was required to workaround dependency and order problems on package removal where the naemon-thruk-libs packages was removed before naemon-thruk. 8. Fixed upstream 9. What exactly is the problem here? Should we just skip the devel package? Or should we provide full %attr? 10. .o is the file extension for nagios/naemon loadable objects. 11. Fixed upstream 12. This does not skip tests entirely, but does not build extented tests which would require additional dependencies. Since full tests are done on travis-ci, we skiped them during packaging. 13. Dan has to look at this 14. I would go for -doc packages. Since we want to include a copy of the html documentation in the future, this would be a good idea. 15. %docs removed upstream and fixed man page globs. 16. The Perl modules are the reason why we used AutoReqProv:no in naemon-thruk and naemon-thruk-libs. In an ideal world, all required perl modules would exist as packages already, then we could just skip the libs package and use requires entirely. Thruk itself looks like a perl module for cleaner development, but is a catalyst perl application, so it does not provide any perl modules. I could probably rewrite this to use %global __provides_exclude_from ... %global __requires_exclude_from ... 17. %if %{defined suse_version}: We tried to make a universal spec file which fits most systems. We could of course create a fedora only spec file. But i see little benefit, it just creates maintainance overhead. If this is a strict requirement, we could maybe provide a script to automatically remove these tags on building the fedora source packages. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review