-----BEGIN PGP SIGNED MESSAGE-----
Andreas Gruenbacher wrote:
On Wednesday 07 January 2009 23:31:45 Jeff Mahoney
[...] In the past month or so I've put some
into making it easier to do what you're looking to do. The first set of
patches remove almost all of the @VAR@ processing in favor of using RPM
variables. The result is that you'll be able to add a new flavor by
simply changing the %build_flavor variable definition in the beginning
of the file and adding a kernel configuration file.
That change is relatively straightforward, and it already makes is a lot
easier to create a new flavor by hand: The current kernel-binary.spec.in
already contains a %build_flavor definition; we only need to use this
definition instead of the old @NAME@ and @FLAVOR@ (which become
kernel-%build_flavor and %build_flavor).
Can't we simply change that, even right now?
Sure. Most of the changes I want to implement we could do right now.
Michal reviewed them and was fine accepting them. I just didn't want to
change them at the 11th hour of the enterprise timetable. I have the
patches queued against my v2.6.28-staging tree.
One thing I'm not certain of is of the requirements of the build service
vs. rpmbuild. I've been using rpmbuild to test. My initial testing with
the build service ended up with broken dependencies on kernel-source =
MACRO, etc. Now I understand that the build service has a different way
of handling that dependency, but I don't know if it can handle macros in
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org