Hi Paul,
Sorry for not replying for a few days, but I have been working on 
getting things easier.  Hopefully it will make getting things into the 
contrib area easier.

First, I have gotten the SRPMS's into the contrib area.   That way you 
have some examples of the source rpm's.

Second.  I do have a script that I use to rebuild the kernel module part 
of these rpm's.  It's at the end of this e-mail.  You will notice I'm 
passing several variables to the rpm, if you look through the spec file 
you'll see what they are, and why I'm passing them.

Third. The kernel module rpm's follow our
kernel-module-<package>-<uname -r>
naming format.  It's a bit ugly but the yum in both S.L. 3.0.x and 4.x 
knows how to handle that format.

Forth.  There is a good writeup on writting the source rpm's for these at
http://rpm.livna.org/kernel-modules.html
I'll be honest and say that livna is where I got some of my original 
spec files from.  (ati, nvidia)

And last
It looks like you have everything setup in your ftp area.  Did you want 
me to put those in the contrib area, or should I wait until you change 
the kernel module part?

Troy

-------------------
#!/bin/bash
BASE="/ide/rpms/troy"
SRPMS="ndiswrapper-1.5-0.SL.1.src.rpm nvidia-glx-1.0.7676-0.SL.1.src.rpm 
ati-fglrx-8.18.6.1-0.SL.1.src.rpm 
kernel-module-qcusb-2.6.9-22.0.1.ELsmp-0.6.3-2.SL4x.src.rpm"

KERNEL=2.6.9-22.0.1.EL
if ! [ "$1" = "" ] ; then
         KERNEL="$1"
fi
echo "Using Kernel: $KERNEL"

for file in $SRPMS
do
echo $file
rpmbuild --rebuild --target i686 --define "ksrc 
/lib/modules/$KERNEL/build" --define "kernel $KERNEL" --without userland 
${BASE}/SRPMS/${file} > ${BASE}/status/$file.$KERNEL.out 2>&1
grep -q "^Wrote" ${BASE}/status/$file.$KERNEL.out
if [ $? -eq 0 ] ; then
         echo "$file : success"
         mv -f ${BASE}/status/$file.$KERNEL.out 
${BASE}/status/complete/$file.$KERNEL.done
else
         echo "$file : failed"
fi
done

-- 
__________________________________________________
Troy Dawson  [log in to unmask]  (630)840-6468
Fermilab  ComputingDivision/CSS  CSI Group
__________________________________________________