[maemo-developers] Dealing with fcam-drivers and different kernels
From: Attila Csipa maemo at csipa.in.rsDate: Fri Aug 6 23:25:24 EEST 2010
- Previous message: Dealing with fcam-drivers and different kernels
- Next message: Controlling N900 Display Brightness & Display turn on
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Monday 02 August 2010 20:38:11 Eino-Ville Talvala wrote: > With the idea that fcam-drivers is preferred since it's a real package, > and fcam-power-drivers only used in case fcam-drivers conflicts? > > Any advice would be appreciated! Off the top of my head, I would do something like: fcam-stock-drivers: Provides: fcam-drivers Conflicts: kernel-power, fcam-drivers Replaces: fcam-drivers fcam-power-drivers: Provides: fcam-drivers Depends: kernel-power (= exact-version) Conflicts: fcam-drivers Replaces: fcam-drivers Then FCam applications would use: Depends: fcam-drivers In plain English - make fcam-drivers a virtual package and indicate with "Replaces:" what package needs to be considered for removal in case of a conflict. Why depend on the flasher ? You can have kernel-power without the flasher. I think it is wrong (but probably safer) that kernel-power does not conflict with kernel. Also, I would be adding some versioning to the kernels as doing modules without depending on EXACT versions of kernels is just asking for trouble (for stock you can count it to be stable between PRs, but kernel- power can change fairly often, with no guarantee of compatibility). And last but least - if you can get the maintainer of kernel-power to include your modules, that would be the simplest solution of them all, then you would have fcam-drivers as is, but kernel-power would have to incorporate: Provides: fcam-drivers Replaces: fcam-drivers Conflicts: fcam-drivers Best regards, Attila
- Previous message: Dealing with fcam-drivers and different kernels
- Next message: Controlling N900 Display Brightness & Display turn on
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]