Package Details: linux-next-git-headers 20250424.r0.g393d0c54cae3-1

Git Clone URL: https://aur.archlinux.org/linux-next-git.git (read-only, click to copy)
Package Base: linux-next-git
Description: Headers and scripts for building modules for the Linux NEXT kernel
Upstream URL: http://www.kernel.org/
Licenses: GPL-2.0-only
Submitter: Nefelim4ag
Maintainer: ptr1337 (gromit)
Last Packager: gromit
Votes: 18
Popularity: 0.177750
First Submitted: 2014-10-12 19:04 (UTC)
Last Updated: 2025-04-27 17:50 (UTC)

Latest Comments

« First ‹ Previous 1 .. 7 8 9 10 11 12 13 14 Next › Last »

Nefelim4ag commented on 2014-10-11 23:47 (UTC)

@denspirit, may be you know why yaourt feature DEVELSRCDIR="/var/tmp/yaourt-build" Working for other git packages like linux-git and zsh-git But not work for linux-next package?

denspirit commented on 2014-10-11 19:03 (UTC)

config.* files (as well as PKGBUILD) were mindlessly stolen from linux-git package, and I apologize for that.

Nefelim4ag commented on 2014-10-11 18:40 (UTC)

using env var for config is awesome, thanks. Just a big thanks.

brenton commented on 2014-05-09 00:50 (UTC)

a suggestion to make the PKGBUILD a bit better: pkgver=next.$(date -u +%Y%m%d)

denspirit commented on 2013-11-18 00:40 (UTC)

Linux-next is an experimental kernel branch, so shipping some default configs is slightly impractical, in my humble opinion. Old PKGBUILD did not use any default configs and relied on user. I stole/inherited a PKGBUILD and default kernel configs from linux-git by xduugu, correcting package names where necessary. X.509 crypto-module could not build,possibly due to a code error, so I disabled it in config.x86-64 and config.i686. While I am posting this PKGBUILD, modules are still building, so I will be sure it works only at morning. If something goes wrong, I will update PKGBUILD again.

enunes commented on 2013-11-17 22:18 (UTC)

I agree. There's also linux-git in the AUR which at least is already updated to the newer git PKGBUILD format.

denspirit commented on 2013-11-17 22:17 (UTC)

True. Relying on makepkg new VCS capability is not suitable for large projects due to the deletion of 'src' every time to update. Will be uploaded soon. Sorry for inconvenience.

paraxor commented on 2013-11-17 22:15 (UTC)

Perhaps it would be prudent to redo this package based on core/linux.

enunes commented on 2013-11-17 22:05 (UTC)

This package isn't building with the uploaded PKGBUILD: -> Skipping tree update... sed: can't read scripts/depmod.sh: No such file or directory ==> ERROR: A failure occurred in build(). Aborting... Why isn't the PKGBUILD posted two comments ago uploaded? While at it, using the PKGBUILD from pastebin, may I give a few improvement suggestions: - Why does this package request user interaction? My build stopped at "Press ENTER if you want to build the kernel or CTRL+C to abort". I don't think that question adds any value to the build process. Also this requires me to sit in front of my PC when building this (one can't build it automatically or just run makepkg and go grab coffee). - This PKGBUILD could be updated to meet the VCS PKGBUILD Guidelines, there's a template for git packages at: https://wiki.archlinux.org/index.php/VCS_PKGBUILD_Guidelines#A_sample_Git_PKGBUILD the prepare() PKGBUILD function could be used to do the rest of stuff in fetch_sources. - This is more questionable but couldn't it just try to borrow the -ARCH config and do oldconfig or zcat /proc/config.gz > .config as fallback instead of failing if I don't provide a .config in the PKGBUILD directory? - In my opinion, mentioning yaourt in the package description is poor practice, that whole second sentence doesn't seem necessary. - namcap throws some warnings: PKGBUILD (linux-next) E: Split PKGBUILD needs additional makedepends ['kmod', 'linux-firmware', 'mkinitcpio'] to work properly PKGBUILD (linux-next) E: File referenced in $startdir PKGBUILD (linux-next) I: Missing Contributor tag PKGBUILD (linux-next) W: Description should not contain the package name.

paraxor commented on 2013-09-12 00:01 (UTC)

@denspirit: Would you like to adopt this package?