On Wed, Dec 15, 2010 at 21:49, Bernd Stramm <[email protected]> wrote: > On Wed, 1 Dec 2010 14:33:29 +0000 > Andrew Flegg <[email protected]> wrote: > >> >> Ultimately, everything's being done for *some* reason on MeeGo. > > Why does the reason for a new release have to be in MeeGo?
Sorry, I mean the repackaging of an upstream release is being done for some MeeGo-related reason; whether it's "we want to track the latest release" or "feature #1234 requires v1.2.3 of liblib or higher". > In such cases, the reason would be documented somewhere upstream. Indeed. But there should then be an issue explaining why that upstream version's coming into MeeGo: >> Perhaps a placeholder issue (per release/milestone) for some rapidly >> developing library which is primarily targetting MeeGo would be >> sufficient? For example, it could be a feature of the form "Provide a >> mechanism for applications to start quickly" which is met my >> *multiple* changes to applauncherd. Cheers, Andrew -- Andrew Flegg -- mailto:[email protected] | http://www.bleb.org/ Maemo Community Council member _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
