On Tue, Nov 18, 2008 at 11:49, Lisha Sterling <[EMAIL PROTECTED]> wrote: > Hi Tero, > >> I'm compiling dependencies into one big package and installing it all >> under /opt/nnn together with the app. > > It's more than sub-optimal. It means that each of our applications > are going to be insanely heavy compared to what they actually need to > be. It also means that the resources of Midinux-running devices are > going to be eaten up at a record speed. > > What this means is that we have none of the benefit of cooperation > and sharing that you get from open source and none of the benefit of a > company giving you all the libs and support you need when it's all > closed source. Am I the only one who thinks that this is utterly nuts?!
I agree with you. This approach works well enough with "single application" embedded systems but not so well for MIDs which are supposed to run 3rd party applications (many of them having dependencies that fall outside Moblin specification). Building a new package repository on top of Midinux would require effort and resources. Any takers? ;) -- Tero _______________________________________________ Moblin dev Mailing List [email protected] To manage or unsubscribe from this mailing list visit: https://lists.moblin.org/mailman/listinfo/dev or your user account on http://moblin.org once logged in. For more information on the Moblin Developer Mailing lists visit: http://moblin.org/community/mailing-lists
