Hi, Niels Breet wrote: > The issue people see is that they are then trying to install the PR1.2 > built application on a pre PR1.2 device. This might or might not work, > depending on which dependencies are specified.
To summarise, from the point of view of a developer: * If I upload a new verrsion of an app which is in Extras, the new version will be built with PR 1.2, and will go into Extras-devel. The old version will no longer be installable from Extras on a PR 1.1.1 device * If I try to test my application from Extras-devel on a PR 1.1.1 device, there is a good chance the application will not install, or will break * The only solution if I want my app to continue being available in Extras is to wait for the PR 1.2 firmware to be released, and not upload any updates Is that correct? And from the point of view of a user, an application which was previously available is no longer available if the developer has tried to update it recently? I don't really understand why uploading an app to extras-devel has hidden the app which is in extras (PR 1.1.1). Isn't that a bit like if I uploaded a package to Squeeze & no-one could download it for Lenny any more? If I don't understand the issue correctly, excuse me, but I'm unclear how you expected things to happen with the autobuilder change. Was the idea that there would be a short period between the SDK and the firmware release, and thus developers could start getting their apps into extras for PR 1.2 before the firmware got released? But in that case, they would need a way to test apps & promote them from extras-devel to -testing & -extras-1.2, no? > * Look at the possibility of adding a hacked libhildon package in the > builder, so it generates 'correct' dependencies and applications can be > installed on PR1.1 if they don't use the new livesearch api. (Probably > most of them) I don't understand this - perhaps you could explain? > * Discuss how we can improve this situation for the next SSU. How about separate repositories? How difficult would it be to have 2 auto-builder targets, and 2 different extras, extras-testing & extras-devel repositories? The defaults wouldn't change for developers, and to test building against the new SDK, you'd just upload to the new autobuilder (where internal Nokia testers could test & promote)? > Trying to do the right thing, I have the feeling that it backfired. :( These things happen - perhaps if we understood the goals you were trying to achieve, there's a way to mitigate against this for the next time. Cheers, Dave. -- maemo.org docsmaster Email: dne...@maemo.org Jabber: bo...@jabber.org _______________________________________________ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
