On Tue, Jul 10, 2012 at 5:21 AM, Ozan Çağlayan <ozancag@xxxxxxxxx> wrote: >> >>> or ckmake with 'sudo'. >> >> How about instead having ckmake detect first if you have your >> $HOME/ksrc/ and if so use that, otherwise go with the built in stuff ? > > This way, if you do not have $HOME/ksrc (which is the case when you > first run get-compat-kernels on a clean system), you will fallback to > the case where the script downloads and extracts the debs into > /usr/src which will again make sure that you will not have $HOME/ksrc > in the next run. How will we populate $HOME/ksrc? What if get-compat-kernels runs differently depending on what user runs it: if you are root, stuff into /usr/src, otherwise $HOME/ksrc/. Then ckmake will simply check if $HOME/ksrc/ is there and use that if its there, otherwise it will simply use whatever kernel headers you have in place in /usr/src -- this is regardless of whether or not you used get-compat-kernels as root or never used it at all. Luis -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
