You are not logged in.
1. Why is firmware a separate package now? Is there a practical reason why we'd want firmware to be a different version than the rest of the kernel? (Or no firmware for that matter?)
2. Why do the ARCH patches recreate ".orig" files? This makes the patch needlessly huge as you can tell patch to do this with "-b".
3. Why is the _kernelname variable set to ${pkgname#kernel26}? As far as I can tell this sets it equal to nothing as there is no variable called pkgname#kernel26. I mean, just try this script:
#!/bin/bash
pkgname=kernel26
_kernelname=${pkgname#kernel26}
echo ${_kernelname}
Thanks for telling me what I can't figure out!
6EA3 F3F3 B908 2632 A9CB E931 D53A 0445 B47A 0DAB
Great things come in tar.xz packages.
Offline
\
3. Why is the _kernelname variable set to ${pkgname#kernel26}? As far as I can tell this sets it equal to nothing as there is no variable called pkgname#kernel26. I mean, just try this script:#!/bin/bash pkgname=kernel26 _kernelname=${pkgname#kernel26} echo ${_kernelname}
Thanks for telling me what I can't figure out!
That allows for easy customization. e.g. pkgname=kernel26-snapshot then _kernelname=-snapshot. You can then append that on to file names etc.
Offline
1. Why is firmware a separate package now? Is there a practical reason why we'd want firmware to be a different version than the rest of the kernel? (Or no firmware for that matter?)
This is to avoid firmware files conflicts when installing a custom kernel. Previously, you had to use the force flag in pacman or it would complain about files already existing and abort the install.
Offline