Re: Packaing question: need some includes from kernel source
On Tue, Nov 19, 2013 at 06:05:20PM +0100, Dridi Boukelmoune wrote: > Maybe this should be added to an existing package. I forgot to mention > that during a review I was told not to have multiple sources. > The main reason is so that the two packages can evolve independent of each other. You don't want to have to update your package because the other source changed. That would seem to apply here as well. -Toshio pgpINYcX0Jklg.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Packaing question: need some includes from kernel source
On Tue, Nov 19, 2013 at 01:31:20PM -0600, Chris Adams wrote: > Once upon a time, Matthew Garrett said: > > If the headers describe a stable interface that should be used by > > userland then it's a kernel bug that they're not being exported. If they > > don't, you shouldn't use them. > > I believe the headers describe what is intended to be a stable > interface. Would that be something I should bring up on linux-kernel? Probably better to look the driver up in MAINTAINERS and contact the people there. > If the interface is supposed to be stable, asking upstream kernel to > change isn't going to help make a package any time soon (and likely > never for EPEL). Is it permissible to carry the necessary headers in > the SRPM until they are no longer needed? From a technical perspective? Sure. Better to do that than add a gratuitous additional package. -- Matthew Garrett | mj...@srcf.ucam.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Packaing question: need some includes from kernel source
Once upon a time, Matthew Garrett said: > On Tue, Nov 19, 2013 at 10:47:12AM -0600, Chris Adams wrote: > > I'm looking at packaing mpt-status (get status info from LSI MPT SAS > > RAID controllers) for Fedora and EPEL. However, to build, it needs some > > include files from the kernel source, specifically from the > > drivers/message/fusion directory. I've built an RPM using an extra > > tarball of all the .h files under that directory (using the 3.11.7 > > kernel source), and it works (and it also works on an older kernel under > > RHEL 6). > > If the headers describe a stable interface that should be used by > userland then it's a kernel bug that they're not being exported. If they > don't, you shouldn't use them. I believe the headers describe what is intended to be a stable interface. Would that be something I should bring up on linux-kernel? If the interface is supposed to be stable, asking upstream kernel to change isn't going to help make a package any time soon (and likely never for EPEL). Is it permissible to carry the necessary headers in the SRPM until they are no longer needed? -- Chris Adams -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Packaing question: need some includes from kernel source
On Tue, Nov 19, 2013 at 10:47:12AM -0600, Chris Adams wrote: > I'm looking at packaing mpt-status (get status info from LSI MPT SAS > RAID controllers) for Fedora and EPEL. However, to build, it needs some > include files from the kernel source, specifically from the > drivers/message/fusion directory. I've built an RPM using an extra > tarball of all the .h files under that directory (using the 3.11.7 > kernel source), and it works (and it also works on an older kernel under > RHEL 6). If the headers describe a stable interface that should be used by userland then it's a kernel bug that they're not being exported. If they don't, you shouldn't use them. -- Matthew Garrett | mj...@srcf.ucam.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Packaing question: need some includes from kernel source
Maybe this should be added to an existing package. I forgot to mention that during a review I was told not to have multiple sources. On Tue, Nov 19, 2013 at 5:59 PM, Chris Adams wrote: > Once upon a time, Dridi Boukelmoune said: >> Hi, >> >> Is kernel-headers enough ? >> https://apps.fedoraproject.org/packages/kernel-headers > > I should have mentioned that neither kernel-headers nor kernel-devel has > the necessary headers. > > -- > Chris Adams > -- > devel mailing list > devel@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/devel > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Packaing question: need some includes from kernel source
Once upon a time, Dridi Boukelmoune said: > Hi, > > Is kernel-headers enough ? > https://apps.fedoraproject.org/packages/kernel-headers I should have mentioned that neither kernel-headers nor kernel-devel has the necessary headers. -- Chris Adams -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Packaing question: need some includes from kernel source
Hi, Is kernel-headers enough ? https://apps.fedoraproject.org/packages/kernel-headers Dridi On Tue, Nov 19, 2013 at 5:47 PM, Chris Adams wrote: > I'm looking at packaing mpt-status (get status info from LSI MPT SAS > RAID controllers) for Fedora and EPEL. However, to build, it needs some > include files from the kernel source, specifically from the > drivers/message/fusion directory. I've built an RPM using an extra > tarball of all the .h files under that directory (using the 3.11.7 > kernel source), and it works (and it also works on an older kernel under > RHEL 6). > > Is this allowed under the packaging guidelines, or is there a better > way? > -- > Chris Adams > -- > devel mailing list > devel@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/devel > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
