On Sat, 26 Nov 2005 18:47:38 +0100, Holly Bostick wrote:
1) disable the symlink USE flag and manage the redirect manually, which
would enable me to download any kernel at any time without concern for
whether a kernel module was upgrading in the same operation; or
That's one approach. In some
Abhay Kedia [EMAIL PROTECTED] writes:
imho that is certainly not the way things should work. Why not build with
latest libraries when you already have them? To do what you want, all kernel
packages will have to be left alone from dependency tracking and I don't know
whether it is possible
OK, I take it back.
I said that the situation of upgrading a kernel with the 'symlink' USE
flag active occurring at the same time as a (particular) program needing
to compile against a configured kernel was not likely to occur all that
often, but I was wrong. It's happened again today, but with a
On Sat, 26 Nov 2005 14:06:02 +0100 Holly Bostick [EMAIL PROTECTED]
wrote:
| Am I doing things wrong, or is this a valid enhancement request for
| b.g.o?
Unlikely to happen... Dependency resolution doesn't work that way.
--
Ciaran McCreesh : Gentoo Developer (The one that looks before leaping)
Holly Bostick wrote:
OK, I take it back.
I said that the situation of upgrading a kernel with the 'symlink' USE
flag active occurring at the same time as a (particular) program needing
to compile against a configured kernel was not likely to occur all that
often, but I was wrong. It's happened
Zac Medico schreef:
Holly Bostick wrote:
I said that the situation of upgrading a kernel with the 'symlink'
USE flag active occurring at the same time as a (particular)
program needing to compile against a configured kernel was not
likely to occur all that often, but I was wrong. It's
Holly Bostick wrote:
This sounds great, but what about the kernel I'm booted into, against
which the module will *not* be compiled, if I have to reboot before
actually configuring/compiling/installing the new kernel?
You can get pretty close to your desired behavior (merge kernel last) if
Zac Medico schreef:
Holly Bostick wrote:
This sounds great, but what about the kernel I'm booted into,
against which the module will *not* be compiled, if I have to
reboot before actually configuring/compiling/installing the new
kernel?
You can get pretty close to your desired
On Sun, 27 Nov 2005 06:47, Holly Bostick wrote:
1) disable the symlink USE flag and manage the redirect manually, which
would enable me to download any kernel at any time without concern for
whether a kernel module was upgrading in the same operation; or
snip
I guess I'll go for option 1, but
9 matches
Mail list logo
