(Sorry: broken quoting)
Which architects? The MeeGo ones should be on this list and
participating in this thread. There certainly shouldn't be backchannel
conversations going on ("meego-dev seems to want repo-oriented
dependencies"/"no") with you having to act as the poor middleman!
Cheers,
Andrew
On 08/09/2010, 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.
>
>> 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...
>
> 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.
>
>
--
Andrew Flegg -- mailto:[email protected] | http://www.bleb.org/
Maemo Community Council chair
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
