Hide Forgot
Description of problem: Since rpmdevtools already provides various sample spectemplate-XXX.spec examples, why not include one for rpmfusion? Version-Release number of selected component (if applicable): 8.2-1 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 557104 [details] Sample rpmfusion -kmod spec file. Cut and pasted from the Wiki kmod2 section plus some additional changes for: (1) reducing repetitive edits (i.e. use macros more); (2) add support for building the userland (-common) subpackage simultaneously;
I'm not totally convinced this should be in rpmdevtools, but... Please remove the -common subpackage, because this should only go in the userland package. See RPM Fusion's "omnibook" package as an example.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Marking as FutureFeature so this doesn't get auto-closed. I am still thinking that this probably belongs in RPM Fusion.
(In reply to comment #4) > I am still thinking that this probably belongs in RPM Fusion. Me too. Unfortunately rpmdev-newspec is not too extensible so at least users would have to use the -t/--type option to get newspec to use it, but until someone improves newspec, I'm afraid this is what we'll need to live with.