On Thu, 2010-07-29 at 10:49 -0700, Arjan van de Ven wrote: > > > > On Thu, Jul 29, 2010 at 10:57 PM, Greg KH <[email protected] > > <mailto:[email protected]>> wrote: > > > > On Thu, Jul 29, 2010 at 09:14:43AM -0700, Arjan van de Ven wrote: > > > On 7/29/2010 1:35 AM, Andrew Wafaa wrote: > > > >Aloha all, > > > > > > > >I'm having some issues getting the network panel to display > > properly > > > >using NetworkManager as the backend via network-manager-netbook. I > > > >appreciate MeeGo uses connman and that is upstream's preferred > > method, > > > >but us mere mainline distros use& like NM ;) > > > > > > > > > > > are you suggesting that MeeGo is not a mainline distro ? > > > > No, he's just saying that NM supports a lot of things that conman does > > not at this time, which is required by other distros :) > > > > I can also suggest a scenario for this. When someone tries to provide > > a distro specific flavor of MeeGo. For example Fedora 14 is supposed > > to have a MeeGo desktop component similar to the Moblin ones they > > had before. And later that usually leads to a Fedora MeeGo spin. In a > > case like this it would be much convenient to get rest of the MeeGo > > components running with the distro infrastructure (i.e. software) at > > hand. Even if they have no case against ConnMan, being able to use > > NetworkManager (and related) makes much sense. > > at this point, Fedora is not going to be able to call this "MeeGo", > or use any of the visual assets that reference MeeGo... because > of things like this connman-vs-NM. > > MeeGo is an OS, not just a UI, and compliance and trademark are very > closely tied to compatible... >
I'm slightly bemused as to how a request for help can be construed as defamation, but never mind. I appreciate that MeeGo is a distro within its own right, my comment would probably have been better if I had used "more common" or "bigger". My issue still remains, could someone advise on what has changed from Moblin 2.1 to MeeGo 1.0 that would render what used to work inoperable? Is it an API change or is there something else? There appears to be a major attitude change along with the code/version change, almost one of exclusivity and not inclusion - shame. I also appreciate the compliance issue as Rob has already pointed that out to me on IRC. I am not calling my work MeeGo but am giving credit where it is due, and I want to work with MeeGo to ensure as wide an audience as possible can drink from the cup of yummy shininess. I most certainly wouldn't want a certain distro to get all the netbook glory now ;-) Regards, Andy -- Andrew Wafaa IRC: FunkyPenguin. GPG: 0x3A36312F openSUSE: Get It, Discover It, Create It at http://www.opensuse.org
signature.asc
Description: This is a digitally signed message part
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
