A new kernel ebuild for the latest prepatch/rc of the stable 2.4 kernel from kernel.org (2.4.22-pre7 for the submitted ebuild). Reproducible: Always Steps to Reproduce: See attachment
Created attachment 14902 [details] Proposed sys-kernel/prevanilla-sources-2.4.22_pre7.ebuild
Comment on attachment 14902 [details] Proposed sys-kernel/prevanilla-sources-2.4.22_pre7.ebuild I've corrected the description of the attachment.
If I can find someone who will maintain the bumps of a kernel.org {pre|rc} ebuild on a consistant basis, then I will consider this for inclusion in our portage tree. I'll ask around. frogger - are you interested in this?
Yeah, I could do this. Shouldn't be hard to maintain bumps to this on occassion, and it's something I'd like to see in portage. How are we planning to handle these _pre ebuilds? I sent an email out to -dev asking for input on this.
best just to put a pkg_postinst warning similar to the one from http://www.kernel.org/prepatch.html. I think this is better than putting the ebuilds in the package.mask. I would also want the package to be 'sys-kernel/vanilla-prepatch-sources' or 'sys-kernel/prepatch-sources'. Probably the first. This would keep users wanting the latest stable version, as deemed by kernel.org, from accidentally emerging the wrong vanilla-sources. So, if you are willing to maintain it with a warning like this, I'd say go for it. Jay
I just committed this in sys-kernel/vanilla-prepatch-sources. I added a pkg_postinst warning basically saying this isn't stable and don't report bugs about it to us. Changed keywords all to ~ (unstable) since this is a prerelease. Otherwise the ebuild is as submitted. Thanks Ian Abbott. I'll be keeping up with the prereleases to update this as necessary. If I get behind, somebody poke me. Closing the bug now.
