For my part I always try to make it obvious what you need to change in a
PKBUILD to build against a different kernel. The use of `uname -r` in a
PKGBUILD to identify the current running kernel and build against that
is something that I think many of us are trying to crack down on. A
binary pkg is always built against a specific version and as Damir said
the PKBGUILD should reflect that version, not be hidden by `uname -r`.
I'm having a similar "disagreement" with ziggy re: the Archie unoinfs
module.
Phil
James Rayner wrote:
On 9/28/05, Andrew Conkling <[EMAIL PROTECTED]> wrote:
On 9/27/05, Tom K <[EMAIL PROTECTED]> wrote:
What's the problem with booting into the new kernel, and then building
your drivers? That's what I do with wlan-ng.
And it's what I do with madwifi. But being able to make sure packages
build (especially madwifi with no release schedule) while still on an
operable kernel is quite nice; if I have any errors, I can resolve
them (usually via my working driver) without rebooting again.
It's just discussion of a feature request/workaround....
Just change the path to the source directory in the PKGBUILD and makepkg.
Otherwise though, most people dont mind booting the new kernel and
making the package there, so its unlikely that a new variable will be
introduced just for that purpose.
--
iphitus - archck maintainer
Home:iphitus.loudas.com Blog: iphitus.blogspot.com
_______________________________________________
arch mailing list
[email protected]
http://www.archlinux.org/mailman/listinfo/arch
_______________________________________________
arch mailing list
[email protected]
http://www.archlinux.org/mailman/listinfo/arch
