Jeff Mahoney wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Matt Sealey wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Matt Sealey wrote:
Ideally, I'd just like to have a kernel-binary.spec where you do - --define "build_flavor $flavor" on the rpmbuild command line but I'm not sure how we'd go about automating the creation of all the different flavors. Okay. I always did --eval "%define jobs 8" and suchlike, now I find
Jeff Mahoney wrote: there's a prettier way to do it with less work, awesome :]
For now, you'll have to continue what you're doing. Look for the v2.6.28-staging flavor in the KOTD archive, and you should be able to use the spec files from there once I add those changes in. Okay. I see the pre/post/preun/postun scripts have the same @BLAH@ processing in it. Do you think this could be changed too? It's really hard to test it without building a kernel, extracting scripts and trying them out manually after installing that kernel. It's kind of a long-winded process.. it takes 10 minutes to build the source RPM here and then another couple of hours to install it, then build the entire thing from scratch (from /SOURCES/kernel-flavor.spec), including all the manual handholding and cigarette breaks.
[1] It's not that there's anything particularly sensitive in there, just that we only have so many hours in the day and it's generally better spent fixing bugs. :) Okay. Actually I have a prudent question about scripts.. is it possible to insert a set of scripts into an already-built RPM? Since testing them out is a complete bitch without ++hours of kernel building here?
-- Matt
The @BLAH@ parts of the scripts get generated from the spec file, not from our external scripts. I'm not a fan of it either, but it shouldn't be a problem.
for script in preun postun pre post; do sed -e "s:@KERNELRELEASE@:$KERNELRELEASE:g" \ -e "s:@IMAGE@:$image:g" \ -e "s:@FLAVOR""@:genesi:g" \ -e "s:@SUBPACKAGE@:kernel-genesi$sub:g" \ -e "s:@BASE_PACKAGE@:$base_package:g" \ -e "s:@RPM_VERSION_RELEASE@:%version-%release:g" \ %_sourcedir/$script.sh > ../$script$sub.sh done Ah I see it's this right? Sigh.. -- Matt -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org