I don't know if any one find this usefull, but I want to post it here so maybe others searching for VIA EPIA kernels could profit from this ebuild. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 39858 [details] epia-development-sources-2.6.8.1-r1.ebuild create a directory for the portage overlay and save the ebuild there in sys-kernel/epia-development-sources/epia-development-sources-2.6.8.1-r1.ebuild then use "ebuild .../sys-kernel/epia-development-sources/epia-development-sources-2.6.8.1-r1.ebuild digest" to download the files and create the digest. then emerge it ;)
what is different from this and the normal g-d-s ebuild? I _really_ do not want to create more kernel packages, we are trying to consolidate them all into one as it is.
Oh, and my main point is that these patches should be sent to upstream so that they will get supported in g-d-s, and _all_ users of linux will benifit. If upstream has rejected them for a valid reason, then we don't want it in our packages either.
What is g-d-s? Gentoo Development Sources? About the patches: They are specific for VIA EPIA systems. I don't know if any other architecture does profit from those patches? And I did not expected you to push them into portage. Maybe introducing a use flag for EPIA systems wich downloads then the specific patch set for EPIA systems could be a better solution? cheers Steve
Yes, g-d-s is "gentoo-development-sources". But, even if these patches only help out one platform, why are they not in the mainline kernel tree so that all users have an easier time using that platform? Please get the patches into the mainline kernel, and then no additional kernel .ebuild for this platform will be necessary.
I am not the developer of the those patches. I only use them. And since the Gentoo forum is full of users using VIA EPIA systems, I was thinking, that adding a ebuild to bugs.gentoo.org for the EPIA systems would be a good thing. But maybe I am wrong and I would better not have them posted here? cheers SteveB
Again, it would be better to get these patches into the main kernel.org tree. That way all gentoo and other users would automatically be able to use them, without having to patch their kernels. Is there anything preventing these patches from being submitted to the proper kernel maintainers for inclusion in the main kernel trees? Please read the file Documentation/SubmittingPatches in the kernel source tree for information on how to submit a kernel patch. And if you have any questions about it, please feel free to ask on the linux-kernel mailing list.
