You are not logged in.
Suppose Archlinux's kernel builds have moved on to version 4.18.x. Is it possible for me to still build a 4.17 kernel using ABS?
Offline
Yes just checkout the commit of the 4.17 based release of linux you are interested in.
Edit:
git clone git://git.archlinux.org/svntogit/packages.git --single-branch --branch "packages/linux"
cd packages/
git log #from the log found the commit for 4.17-1
git checkout 19e67dc25af64dcdc15c365fba6378db45a23d2f
cd trunk
cat PKGBUILD #confirm this is the version you want then build as normal
Last edited by loqs (2018-06-26 13:32:42)
Offline
Yes just checkout the commit of the 4.17 based release of linux you are interested in.
Edit:git clone git://git.archlinux.org/svntogit/packages.git --single-branch --branch "packages/linux" cd packages/ git log #from the log found the commit for 4.17-1 git checkout 19e67dc25af64dcdc15c365fba6378db45a23d2f cd trunk cat PKGBUILD #confirm this is the version you want then build as normal
What if the 4.17 version I want is not one that Arch ever used? Say, for instance, I wanted to build 4.17.8, but Arch had switched to the 4.18 series after 4.17.7. They wouldn't have 4.17.8 in their tree. Could I still build 4.17.8 using ABS?
Offline
Pick that last version arch provided then update pkgver to the version you want then run updpkgsums to update the checksums.
Or start with linux-git change the git tree to linux-stable set the commit/tag for the release you want and ensure the .config is the one you want.
Offline
Pick that last version arch provided then update pkgver to the version you want then run updpkgsums to update the checksums.
Or start with linux-git change the git tree to linux-stable set the commit/tag for the release you want and ensure the .config is the one you want.
Cool, thanks.
Offline