I send an email to Judd concering this a few weeks ago, but I haven't
got an answer from him so, and I quote what I said:
"I was thinking about their new x.y.z.a release schedule, and I was
thinking to reduce kernel upgrades which require a reboot, how to
release the packaged kernel:
When for example 2.6.12 comes out, we package 2.6.11.11, the latest
stable version of 2.6.11
When 2.6.13 comes out, we package 2.6.12.a (where a is the number of the
final release of 2.6.12)
I think this would be the most stable solution, especially on servers."
Judd Vinet wrote:
Hello all,
As you all well know by this point, the kernel developers have taken to
releasing minor updates every week or so (2.6.12.1, 2.6.12.2, etc.).
This has really increased the kernel maintenance workload for tpowa and
myself, because each kernel rebuild means that all extraneous modules
(nforce, ipw2X00, ltmodem, slmodem, etc.) need to be rebuilt with that
version.
*snip*
_______________________________________________
arch mailing list
[email protected]
http://www.archlinux.org/mailman/listinfo/arch