On Tue, Sep 28, 2010 at 19:57, Eino-Ville Talvala <talv...@stanford.edu> wrote: > [snip] > > Since FCam is a publicly-available API that we're trying to promote, we're > expecting third parties to write applications that depend on fcam-drivers. > That means not all apps will be ours, and we can't do the update for them, > leaving some users with buggy versions. Already, the HDR and low-light > programs are apps by our collaborators at Nokia Research, and I don't have > any ability to update them.
You only need one app to pull up the version with a >= dependency and the fcam-drivers for every app will get updated. If the user-facing application suffers from a bug, them putting out a re-release with an increased dependency once upstream (i.e. you) fixes it shouldn't be too much of a problem. If their app isn't affected by the bug (and no app really is), there's no impact on the user ;-) A little simplistic, but hopefully it helps. Cheers, Andrew -- Andrew Flegg -- mailto:and...@bleb.org | http://www.bleb.org/ Maemo Community Council member _______________________________________________ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
