On 23/05/10 20:32, Graham Cobb wrote:
On Wednesday 19 May 2010 18:50:01 Jeff Licquia wrote:
There could be an issue with newer MeeGo releases, say a MeeGo 1.1 app
running on a MeeGo 1.0 device. But there are other hurdles to cross if
we want to support that model (what to do with new 1.1 functionality,
for instance). As long as we do our job correctly, and 1.0 apps
continue to work on 1.1 devices, then we have at least a 90% solution:
just build your app against the oldest MeeGo version you want to
support.
...
Maemo world. Will the Meego OBS have an easy way to support this (create an
app at at time when version 3.4 is current, build it against version 2.3 and
install it in a repository which will allow it to be found by all users using
versions later than 2.3 including versions that don't exist yet)?
Quite simply : Yes.
The ability to target multiple distros (or distro releases) from a single
project is one of the huge strengths of the OBS.
I am hoping that the community OBS will allow you to target:
Fremantle x86/ARM
Harmattan x86/ARM
MeeGo 1.0 x86/ARM
Harmattan+1-from-Nokia x86/ARM
MeeGo-from-IVI x86/ARM
and even:
Ubuntu:10.04 x86/ARM
Debian:5.0 x86/ARM
All from the same tarball/git repo.
There are no *technical* blockers to doing all this on the one community OBS.
I'm not aware of a reason we can't support Diablo and even older too... we'd
need volunteers to setup and manage the buildroot port... a process which is
very well documented (if I do say so myself) here:
http://wiki.maemo.org/OpenSuse_Build_Service/Fremantle_Setup
I also recognise that not all developers agree with my preferred approach.
...
Both sorts of developers exist in the Maemo world today and can be expected in
the Meego world as well, I guess.
And that's fine too.
I'm not sure how this plays out in policy/process for Extras though.
David
--
"Don't worry, you'll be fine; I saw it work in a cartoon once..."
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
