The last discussion how to handle kernel-modules in the buildsys stuck
at some point (for those who can't remember it see
https://www.redhat.com/archives/fedora-buildsys-list/2005-August/msg00030... for the start and https://www.redhat.com/archives/fedora-buildsys-list/2005-August/msg00036... for one of the ends.
I really would like it if we could get this discussion to life again to
solve this problem. I made a quick hack against mock 0.4 so it passes a
"--define kernel\ some-kernel-version-here" to the rpmbuild-calls that
build the pgk. This required a new mock command-line option ("--kernel
put-some-kernel-version-here"). I included a quick check so this option
only works with packages whose name starts with "kernel" so nobody sane
can abuse it for other packages. Warning, I'm not programming very
often, but the patch WORKSFORME. Seth, is something like that acceptable
Dan, if something like that goes into mock -- what would be the best way
to make this new mock-option usable in plague for kernel-modules in
fedora-extras? Should plague automatically build the modules for all
kernels available (the one that was shipped and those currently in
updates-released)? Or only for the newest kernel available? Or should
the packager say something like "make plague KERNEL=put-kernel-ver-here"
when requesting build of a fdr-extras-kernel-module-pkg?
Thorsten Leemhuis <fedora(a)leemhuis.info>
I have repos set up for the base system and also the "built" packages.
Instead of manually commenting these out when the need arises, it can
automatically be scripted using the --disablerepo option to mock. This
is then forwarded to the yum command.
When dealing with building yum itself inside of a mock chroot, it's
better to do this:
yumconf = os.path.join(self.rootdir, 'etc', 'yum.repos.d',
Instead of messing with rpmsave/rpmnew.