Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#3824 - kernel packaging suggestions

Attached to Project: Arch Linux
Opened by maciek (demonus) - Monday, 23 January 2006, 08:11 GMT
Last edited by Jan de Groot (JGC) - Monday, 23 January 2006, 09:44 GMT
Task Type Feature Request
Category Packages: Current
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture not specified
Severity Medium
Priority Normal
Reported Version 0.7.1 Noodle
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I have a few suggestions concerning kernel packages that may appear useful. First of all, if you look at the PKGBUILD for kernel26 there are some nasty hacks copying kernel headers etc.
so what I suggest is to make the following:
package: kernel26-headers -> this one would include all nccessary header that nvidia, lirc or anything else requires (yes some programs do need headers at least)
package: kernel26-sources -> all sources for current kernel with patches that are applied in PKGBUILD for kernel
I would like to know the opinions of others. The way I see it is that the overall manageability of kernel would become simpler:
* in kernel26 PKBUILD -> in makedeps put kernel26-sources, then apply config build install clean
* rebuilding kernel from abs would not have to download new *.tar.bz2 kernel sources each time
* those who do some programming and require headers/source would have a pacman managed package
I hope these points are reasonable enough to think over this solution
This task depends upon

Closed by  Jan de Groot (JGC)
Thursday, 26 October 2006, 21:29 GMT
Reason for closing:  Implemented
Additional comments about closing:  As tpowa says
Comment by maciek (demonus) - Tuesday, 31 January 2006, 13:51 GMT
I would suggest the following for kernel26-source

pkgname=kernel26-source
basekernel=2.6.15
pkgver=2.6.15.1
pkgrel=1
pkgdesc="The Linux Kernel and modules"
url="http://www.kernel.org"
source=(ftp://ftp.kernel.org/pub/linux/kernel/v2.6/linux-$pkgver.tar.bz2)
md5sums=('cdf95e00f5111e31f78e1d97304d9522')

build() {
_localversion="ARCH"
_kernver="${basekernel}${CONFIG_LOCALVERSION}"

mkdir -p $startdir/pkg/usr/src
cp -a $startdir/src/linux-${basekernel} $startdir/pkg/usr/src
mv $startdir/pkg/usr/src/linux-${basekernel} $startdir/pkg/usr/src/linux-${_kernver}
chown -R root.root $startdir/pkg/usr/src/linux-${_kernver}
}

Comment by James Rayner (iphitus) - Thursday, 25 May 2006, 00:03 GMT
* rebuilding kernel from abs would not have to download new *.tar.bz2 kernel sources each time

i think most of this setup is overkill. but to fix this one, I suggest that kernel26 uses 2.6.16 tarball, and then a patch to the latest .y release. Less downloading.

James
Comment by Tobias Powalowski (tpowa) - Friday, 26 May 2006, 06:36 GMT
it is done that way already for ages.

Loading...