On Tue, Sep 7, 2010 at 6:19 PM, Wichmann, Mats D <mats.d.wichm...@intel.com> wrote: > Someone else said there are simply two different models: > the repository-based model where the installer resolves > certain dependencies (and it's easy enough to SAY something like > "may only depend on components of MeeGo core, or from MeeGo > compliant packages"); and one where an app may have no dependencies > at all, basically "depend on MeeGo" is it, everything else is > self contained. > > It seems like the wind is blowing in the direction of the latter, > for all that it's easy to envision very useful uses for the former. > It went in the spec that way based on what people who worked > on this were told; hoping the discussion will make it clear what > the spec actually needs to forbid/allow in this area. >
Seems to me like the wind is blowing in the other direction, at least on this mailing list... For commercial dependencies it might make sense to include everything in one package, just to simplify pricing and distribution. But for open-source dependancies I really don't think it makes sense to disallow non-meego dependancies... 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... Warren -- Warren Baird - Photographer and Digital Artist http://www.synergisticimages.ca _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
