I'm making a customized kernel rpm, based on kernel-2.4.spec from kernel-2.4.20-28.9.src.rpm.
The specfile has a "polite request for people who spin their own kernel rpms" to modify the release field in such a way tht indentifies that the kenel isn't a stock RHL kernel.
That's fine with me. What I'm wondering is if anyone has suggestions on what scheme to use. I'm making an rpm for 2.4.24, and in the event that Red Hat released a supported 2.4.24 kernel rpm, I'd like to make sure that my custom release is numbered in such a way that rpm -Uvh, apt-get, etc all recognize that the Red Hat kernel is newer and should be installed in place of my custom kernel.
If I do something like %define release olin.0.1 in the specfile, is that sufficient?
If I'm totally barking up the wrong tree, that's fine too. Suggestions for better approaches are welcomed.
-- Aaron Bennett UNIX Administrator Franklin W. Olin College of Engineering
_______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
