handy
October 21st, 2008, 08:58 AM
*** Please if you notice the following needs editing due to changes upstream, please PM/email me with the details so I can keep the information current? Thankyou. ***
_______________
Here is some very valuable information that I have lifted from a reply to my questions in the Arch forum (http://bbs.archlinux.org/), asking why recent kernels aren't in AUR & I stated that we need easy access to superseded kernels:
_______________
It is clearly stated in the AUR guidelines:
Check [core], [extra], , and [community] for the package. If it is inside any of those repositories in ANY form, DO NOT submit the package (if the current package is broken or is lacking an included feature then please file a bug report in FlySpray).
However, since all official packages are maintained in a SVN repository, accessing previous kernel versions is as simple as:
. /etc/makepkg.conf
svn export -r[REV] svn://svn.archlinux.org/srv/svn-packages/kernel26/repos/core-$CARCH kernel26
Where [REV] is the revision you want to export. To find out which revision corresponds to which kernel, have a look at: [U]i686 (http://repos.archlinux.org/viewvc.cgi/kernel26/repos/core-i686/PKGBUILD?view=log) or x86_64 (http://repos.archlinux.org/viewvc.cgi/kernel26/repos/core-x86_64/PKGBUILD?view=log).
For example, if I were to get the 2.6.26.x kernel (latest was 2.6.26.5) for the i686 architecture, I'd proceed like this:
. /etc/makepkg.conf
svn export -r12086 svn://svn.archlinux.org/srv/svn-packages/kernel26/repos/core-$CARCH kernel26
_______________
Here is some very valuable information that I have lifted from a reply to my questions in the Arch forum (http://bbs.archlinux.org/), asking why recent kernels aren't in AUR & I stated that we need easy access to superseded kernels:
_______________
It is clearly stated in the AUR guidelines:
Check [core], [extra], , and [community] for the package. If it is inside any of those repositories in ANY form, DO NOT submit the package (if the current package is broken or is lacking an included feature then please file a bug report in FlySpray).
However, since all official packages are maintained in a SVN repository, accessing previous kernel versions is as simple as:
. /etc/makepkg.conf
svn export -r[REV] svn://svn.archlinux.org/srv/svn-packages/kernel26/repos/core-$CARCH kernel26
Where [REV] is the revision you want to export. To find out which revision corresponds to which kernel, have a look at: [U]i686 (http://repos.archlinux.org/viewvc.cgi/kernel26/repos/core-i686/PKGBUILD?view=log) or x86_64 (http://repos.archlinux.org/viewvc.cgi/kernel26/repos/core-x86_64/PKGBUILD?view=log).
For example, if I were to get the 2.6.26.x kernel (latest was 2.6.26.5) for the i686 architecture, I'd proceed like this:
. /etc/makepkg.conf
svn export -r12086 svn://svn.archlinux.org/srv/svn-packages/kernel26/repos/core-$CARCH kernel26