Aaron Griffin wrote:
On Mon, Dec 15, 2008 at 1:32 PM, Tobias Powalowski <[email protected]> wrote:
Am Montag 15 Dezember 2008 schrieb Thomas Bächler:
Tom K schrieb:
No package owns them. They're being produced by depmod since the 3.5
update of module-init-tools.
I could be wrong, but I think the kernel is the only package that calls
depmod in the build function - other packages that need depmod call it
in post_install, which is why these files are not owned.
That is okay. We call depmod in the PKGBUILD so kernel26 will own those
files and they will be properly uninstalled when the kernel is removed
or updated.
After the m-i-t 3.5 update, those .bin files were generated on your
system, but were not contained in the kernel package yet. The new
package is generated with the new m-i-t, thus contains them. We have to
force-upgrade that one so pacman will again be able to track those files
and delete them when appropriate.
Are you guys fine with moving kernel package to core, with this possible file
conflict and make a announcement that forcing is ok?
Yeah, just make sure we indicate that users should -Sf kernel26, not
-Sfyu, which would be a poor recommendation on our part.
Why not solve it the right way, by creating a correct package?
Glenn
