Re: Maemo + Moblin = MeeGo
 

People people people. Admittedly this is a big announcement and change but I just want to chime in on the apps issue.

With Qt4.6 the whole concept of "porting" an app is re-invented. I have written 3 apps using the Qt 4.6 platform since I bought my N900 and the thing that struck me immediately was how easy it was to move from platform to platform.

I run Linux on my desktop, Qt creator runs fine there and I have the scratchbox installed for compiling to ARM. I run windows 7 on my laptop and Qt creator works fine there and I have MADDE installed for compiling to ARM. Regardless of the environment I am on the apps compile and run. All it needs is the libs to be compiled for the platform and we already KNOW they will be for maemo and the N900. So porting an app that is based on Qt (and it sounds like they all will be in the future) is as simple as compiling the app for that platform. Since MeeGo will be multi hardware based (including ARM) I see no reason to believe devs would not compile for all platforms, including ARM.

The second thing to note here is that the ENTIRE OS is going opensource with MeeGo. Should Nokia simply stop supporting us "poor" N900 users then there is nothing stopping us simply compiling the OS for ourselves. No more complaints about closed source media players etc etc.

This is a change - and change can be scary - but if we take a deep breath and realize where this change can take us, I think we will all see the advantages to this merger.

(Heck at a basic level larger devs are certainly going to be looking at this platform with both Nokia AND Intel behind it)

Re: Maemo + Moblin = MeeGo
 

I wonder if this was what they had in mind for "Step 5" when that whole meme got started.

(this is sarcasm, for those who are not attuned to it.)

Re: Maemo + Moblin = MeeGo
 

This hasn't been true for many years now. Using a server-based repository along with yum, apt4rpm, etc. RPMs have no more dependency issue than .debs. The only "issue" as such is that they're far more widely used, therefore you can run into problems if you try to use an RPM from one distribution on another. Using .debs don't magically make you immune to this issue though (it's just that .debs have generally only been used by debian-derived distributions, so core library/application names have been consistent).

Re: Maemo + Moblin = MeeGo
 

It depends on how you define OS, a media player is not really part of the OS, so it could very well be closed source. It could also be that Manufacturers add other proprietary parts (such as drivers, power management code) when they create a release for a specific device.

I hope this will not be the case and Nokia will strive to make a good example and open source as much as possible when they integrate the current Maemo 5 into MeGoo.

Re: Maemo + Moblin = MeeGo
 

Wouldn't that go against the whole concept of this merger? The big push here seems to be that Moblin brings the open OS and Maemo brings the development env.

Re: Maemo + Moblin = MeeGo
 

released today:
http://qt.nokia.com/products/platform/maemo
http://labs.trolltech.com/blogs/2010...mo-5-released/

Bye

Thorsten

Re: Maemo + Moblin = MeeGo
 

RPM? Debian?

OpenWRT doesn't use either. And they're on their 2nd version of a distribution system.

Don't let the Meta code be too important. Open is what matters.

Re: Maemo + Moblin = MeeGo
 

Re: Maemo + Moblin = MeeGo
 

Really? It is a long time since I had a "made in finland" Nokia. Is the Korean N900 line in a Nokia-owned factory?

Re: Maemo + Moblin = MeeGo
 

Yes, the unit in Korea is directly owned by Nokia.