Re: Bug#226779: kernel-package: differences between official and custom builds
On Wed, 9 Feb 2005 01:16:32 +0100, Danilo Piazzalunga <danilopiazza@libero.it> said:
> tags 226779 + patch thanks
> This same bug also hit Ubuntu, and was fixed by Matt Zimmerman with
> the attached patch.
I'm sorry, I am not happy at this resolution, which is merely
symptomatic relief (shuts down a warning when there is a clash
between packages). Bit it still allows an official kernel to override
a user specified kernel of the same name; and worse, since it does it
by silently over writing modules, rather than moving them out of the
way, using the clobber modules version, the user may end up with a
hodge podge of modules from the local build, and some of the official
kernel that is being laid over, which is not a situation we want the
user to end up in. (I understand why i uses silent modules rather
than clobber modules).
If we must have official kernel header packages adding in
symbolic links that are not created by kernel-package, but need to
have kernel-package deal with the resulting situation, a better
solution must be crafted.
First, do not give an official kernel carte blanch to ride
rough shod over any existing modules dir; but only do so if the only
thing currently in that directory is a build symbolic link, and
nothing else. In this case it would be OK to let the build symlink
stand -- assuming that the kernel image itself does not come with
its own build symlink.
manoj
--
You will feel hungry again in another hour.
Manoj Srivastava <srivasta@acm.org> <http://www.golden-gryphon.com/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
Reply to: