On 08/09/10 15:00, Wichmann, Mats D 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.
Can I echo "who said what?"
For commercial dependencies it might make
sense to include everything in one package, just to simplify pricing
and distribution.
Let me fix that:
"Our packaging/install tools aren't up to the job"
... OK.
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...
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.
Well. That's one "solution".
David
--
"Don't worry, you'll be fine; I saw it work in a cartoon once..."
_______________________________________________
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
