Folks,
I've whipped up some new OpenAFS packages based on some of what we have
discussed and proposed regarding kernel module packages. I'm kinda
suprised that Matthew hasn't beaten me to it. :-)
These are a rough first attempt. I have left out the debuginfo package
stuffs for a future exercise. But I invite folks to comment on them.
I'll probably be working on fine tuning these tomorrow during work.
After working on this for a few hours I have come to the conclusion that
the method of doing kernel-module-foo-source packages is very complex.
I'm a big fan of having most of the smarts be in Yum and in this case
the build system rather than depend on complex magic from the packager.
But I do understand the issues of having multiple similar/same SRPMS,
debuginfo packages etc. What's the worst evil? *shrug*
SRPMS:
http://anduril.pams.ncsu.edu/~slack/SRPMS/kernel-module-openafs-source-1....
http://anduril.pams.ncsu.edu/~slack/SRPMS/openafs-1.3.84-6.src.rpm
SPECS:
http://anduril.pams.ncsu.edu/~slack/SPECS/kernel-module-openafs-source.spec
http://anduril.pams.ncsu.edu/~slack/SPECS/openafs.spec
Jack Neely
--
Jack Neely <slack(a)quackmaster.net>
Realm Linux Administration and Development
PAMS Computer Operations at NC State University
GPG Fingerprint: 1917 5AC1 E828 9337 7AA4 EA6B 213B 765F 3B6A 5B89