On Wed, Aug 6, 2014 at 8:11 PM, Markus Falb <markus.falb@xxxxxxxx> wrote:
> On 5.8.2014 03:24, BC wrote:
>
> Why not define the kernel source as buildrequire?
>
Seems quite recursive to me. I would have to list the source rpm for the
various kernels which means I would be bundling a src.rpm into the driver's
src.rpm as well as calling rpmbuild itself from within a spec file. This
would be the RPM way of doing it, at least (I do need to
generate/distribute the src.rpm for the driver). Short of any rpm-specific
way of solving the "my spec file relies on real kernel sources", I'll
probably have make a kernel-sources RPM (not source RPM) that actually
installs somewhere other than $HOME and use that RPM as a buildrequire in
place of kernel-devel, which is insufficient for my need.
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
