On Wed, Sep 8, 2010 at 10:00 AM, Wichmann, Mats D <[email protected]> wrote: > Warren Baird wrote: > >> Seems to me like the wind is blowing in the other direction, at least >> on this mailing list... > > yes it is, I didn't mean to imply otherwise. more that the > architects has seem pretty set on this idea.
As others have said - who are 'the architects'? Can they step up here and give some strong rationales for this approach? I haven't seen anything remotely convincing yet... >> Take a look at any modern linux distro. How many packages are there >> that depend on other 3rd party libraries and tools? It's going to >> make the open-source developers life a lot more complicated if they >> have to bundle *everything* in their package - not to mention the >> wasted disk space, which can be at a premium on a handset... > > I think if there's something used widely enough there's a space > wastage issue by it not being "shared" then there's a case it > belongs in the core after all. That seems horribly inefficient... you are proposing that we automatically add 'widely used enough' libs to the core? Does that mean that when a library is used by N apps, each of the N apps has to bundle it? But when the N+1'st app starts using it, we'll move it into the core, and the other N apps need to redo their packaging to make use of the lib in the core? Limiting commercial dependencies makes perfect sense - no one wants to buy a program for $5, and then find out they need to buy another $40 worth of dependancies to use it... Even limiting dependencies to things available from a 'standard' meego repository might make sense... But having to limit dependancies to the meego core seems like a very bad idea. Warren -- Warren Baird - Photographer and Digital Artist http://www.synergisticimages.ca _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
