On Thu, Sep 16, 2010 at 2:44 PM, David Greaves <da...@dgreaves.com> wrote: > > I think we need to achieve 2 things: > * permit the open-source development model to work for compliant > applications > * define the spec in a way to minimise the imposed burden on vendors >
Thanks for trying to pull things back to the basics --- I think the discussion has kinda gone all over the place... >From what I've seen, I at least do agree with these two goals --- We definitely need a model that will work for hardware vendors - otherwise we won't get anywhere... However, I also think that for many use cases, mandating full inclusion of all dependencies will hurt a lot - it'll cause package bloat, and cause tonnes of old, bug ridden copies of libraries to be floating around on users drives. Earlier in the thread there was discussion around 2 levels of compliance - a 'strict' compliance that requires inclusion of all dependencies, and a more relaxed compliance that allows dependencies on an 'Extras' style repository... To me, this still seems like the best approach - I think we need some kind of official recognition for well-formed, tested apps that include dependencies... Thoughts? 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
