For some reason.. it seems like every question I ask in here grows into a long heated discussion.
Android for example is mostly developed on Ubuntu. You can run it on Windows, Mac, and Every distro of Linux if you want, it seems like the initial instructions that come out are always for Ubuntu first. In theory I could try to tinker with things to make it work, but in general I've found I have less problems if I ran on Ubuntu as my platform of choice. (Btw.. this is all my observation and does not even pretend to be factual in any way) My question initially was if there was a preferred platform for Meego. Just like the statement above, it seemed like trying to build Meego's dev or final-2.1 environment on Fedora was a lot less problematic then the Ubuntu version. I've had a much easier time building Meego on FC. If Nokia's developers generally prefer working on FC, then odds are things will be first documented and more likely to work in the environment they primarily work in. I'm sure it'll work on every flavor of Linux with a bit of work... I'd just rather spend the time on actual code for meego rather then making meego work. That being said... fedora, ubuntu, SuSe... as long as we have a product it doesn't matter what it is based on, used, as long as it works. Also.. the current environment doesn't have a GUI... presuming there is an xorg-server update coming through the yum repos (It seems yum update works quiet well). Can we expect that an application coded for meego will look fairly close to that on the final product? ie. Will Meego come with a custom navigation... wrap around the X11 environment.. I presume that anything I can do on Linux I can essentially do on Meego. Though I presume the UI will be presented in a fairly more user friendly manner then here is an xterm, have fun. -- Samir On Fri, Apr 2, 2010 at 11:22 AM, Arjan van de Ven <[email protected]> wrote: >> Who build the package is not important, what's in the package and the >> quality is more important. >> what I want to express is if the packages without meego's special >> patches, meego should just use/rebuild it from fedora, it reduce the >> cost of the project. > > that sounds nice in theory, but does not work in practice. MeeGo and Fedora > have very different objectives and that makes what you describe not a good > option, > and not current practice. > > As an example, Maemo started with Debian, but current Maemo and Debian are > rather > far apart. > > > MeeGo does borrow some packages from Fedora (like glibc) just like we borrow > some packages > from OpenSUSE. I don't expect this to grow dramatically over time; in fact > as things evolve further > I'd not be surprised if the opposite happens. > _______________________________________________ > MeeGo-dev mailing list > [email protected] > http://lists.meego.com/listinfo/meego-dev > -- -- Samir Faci *insert title* fortune | cowsay -f /usr/share/cows/tux.cow _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
