Messages in this thread | | | From | Frans Pop <> | Subject | Re: [PATCH] firmware: Allow release-specific firmware dir | Date | Thu, 11 Sep 2008 20:24:29 +0200 |
| |
On Thursday 11 September 2008, Linus Torvalds wrote: > On Thu, 11 Sep 2008, Frans Pop wrote: > > > Aren't _you_ the one who are ignoring current issues? > > > > I don't think so. > > _The_ current issue for me is that I can no longer build Debian > > kernel packages using 'make deb-pkg', which is part of _your_ tree, > > and install the resulting package *NOW*. > > Well, complain to the right people then. The patch that started this > all is wrong.
I totally agree with that.
What I would still like to see instead is the *option* to just include firmware inside modules, where it's always been.
Either that, or stop building firmware as part of the kernel build process altogether (which seems to be David's vision of the future).
> The people you are complaining to are not the rigth people. We can't do > anything about debian packaging.
This isn't about Debian packaging or Debian tools. I'm not using a Debian tool [1]! Why is that so hard to understand?
I'm using an option in *your* kernel tree that produces a broken Debian package. Please have a look in scripts/package/builddeb. That offers the option to just do 'make deb-pkg' to build a kernel package in Debian package format.
The other part of my complaint is that this simple example proves that the firmware split *has* broken existing tools while you and others have been maintaining that everything would continue to work fine "because everyone has been using /lib/firmware for ages". The reason things have broken because we never used to generate files as a basically inseparable part of a kernel build before.
[1] I abandoned make-kpkg about a year ago because it was terminally insane and broken. AFAIK it still does not support the unified x86 dir...
| |