Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report.
Summary: Review Request: <libtune> - <standard API to access the kernel tunables>
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=210007
------- Additional Comments From Nadia.Derbey@bull.net 2006-11-23 11:53 EST ------- (In reply to comment #16)
I think I was not specific enough. The thought is that it would be generic enough that when build against a specific release - it would create an RPM against that one.
If I built under FC5, it would build a FC5-tunable package for the kernel that is in FC5. and not a FC6 one.
If I built it under FC6, it would build a FC-6-tunable package for the kernel that is in FC6, and not a FC5 one.
and so on.
This would have to be generic enough so that when FC7 comes, there is no need to alter the SPEC file. Or if it has to be done - just the minum if possible.
OK, I'm conviced
In regards to your comment about "portability across distros" is a moot point. This RPM/SPEC is specific for Fedora Core and RHEL. This spec file will not be used by Novell/SuSE. Novell will have require their own .spec file, with different fields.
Yeah! I know, that's what I have been fighting with these last days! What I meant here was not portability for the spec file, but for a binary linked with the libtune.
I am not sure what you mean by "somebody downloading the kernel database". When the RPM is installed, does it not include all the neccesary data?
We have 1 rpm for the kernel data part and 1 rpm for the more distro-specific part.
Ok I'll change everything and update the bug when I'm ready.