Hi!
I think this problem is serious and we should avoid these critical errors (I also had a glibc error with kernel 2.4 a few years ago). This error cannot be determined automatically by pacman (local db, depends...); so some extra packager work is needed. However, as I know there is no way to do some specific checks now before a package install... A possible solution: we should check the return value of pre-install script (or any other "communication channel" can be implemented), which could abort the install (I imagine an uname test in the script, and a nice question/error message to the user, and return 1 here).
Bye, ngaba
PS: Or we could implement a new scriptlet type, e.g. extra-depends. (This will lead to one of my earlier question (see fileconflicts): what to do if we have to stop the transaction after some packages installed and some other packages are waiting for install yet. So it is better to define extra-depends (similar to the normal depends) as a "pre-transaction argument".)
---------------------------------------------------- SZTE Egyetemi Könyvtár - http://www.bibl.u-szeged.hu This mail sent through IMP: http://horde.org/imp/
_______________________________________________ pacman-dev mailing list pacman-dev@archlinux.org http://archlinux.org/mailman/listinfo/pacman-dev This can be solved by adding a dep for kernel>=x.y.z to glibc, and add a
Nagy Gabor wrote: provide=('kernel') to all kernel images. Andrew