View Single Post
Posts: 946 | Thanked: 1,650 times | Joined on Oct 2009 @ Germany
#59
Originally Posted by rambo View Post
Name
IMO "kernel-community" is better than "kernel-maemo" in indicating that this is indeed not the official maemo kernel and thus will be using that name in the following examples.
There is an offical Nokia kernel. I think maemo is fine and indicates the name of the community. I'll wait for other people's opinions before taking any action.
Packaging ideas
Use Provides liberally to denote features, this way applications can depend on the features and not specific kernel/module package.
Yes, that's a good idea.
I have added the some Provides to the new kernel in extras-devel non-free.
However, there is only a single modules packages, which provides all modules.
It could also symlink the modules, which also work with the stock kernel
to the stock modules directory.
Modularity
Another thing that should be though about sooner rather than later is the fact that everyone wants their favourite feature to the community kernel, this eventually leads to a huge modules package (the symbols that must be in the kernel itself are kind of hard to avoid). It would be better to have the modules as sane collection packages (like "kernel-community-modules-nat" and "kernel-community-modules-joydev" examples above)
I don't think this makes sense. A few kb more or less per module don't justify selecting tens of separate tiny module packages.

The new kernel also contains your hotspot patches and modules.