[maemo-developers] Repositories mess: conclusions and actions
From: Nick Phillips nwp at nz.lemon-computing.comDate: Mon Nov 12 00:32:53 EET 2007
- Previous message: Repositories mess: conclusions and actions
- Next message: Repositories mess: conclusions and actions
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 12/11/2007, at 11:21 AM, Graham Cobb wrote: > I don't think I agree. I am concerned about what will happen when > V4.1 is > issued. For Bora I currently build my packages against 3.0 so that > all > releases of Bora can be supported. I would expect that the same > thing would > happen with Chinook: packages should normally be built against the > oldest > libraries that will work and which do not conflict with the latest > libraries. > Otherwise users may experience unexpected (and partial) upgrades of > base > system components due to installing an application. Will Nokia > test all > possible combinations of partial OS upgrades when 4.1 comes out? > > This is a complex issue which also requires some further thought > from the > point of view of autobuilder requirements. As I wrote a while ago, I'd recommend people interested in this check out Debian policy (http://www.debian.org/doc/debian-policy/) and Ubuntu's equivalent (not sure where you'd find that), and see how and why Debian and Ubuntu deal with these things. There are differences (e.g. Debian requires a binary on one arch to be uploaded, while Ubuntu allows/prefers autobuilding for all), but there should also be some issues that are pretty firmly resolved one way or the other. Cheers, Nick
- Previous message: Repositories mess: conclusions and actions
- Next message: Repositories mess: conclusions and actions
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]