Why would you want to? That might sound flippant, but it's a serious question. If you're building a "proper" CoApp package, the dependencies of which are also already CoApp packages, why would you choose to forego automatically benefiting from (compatible) updates to those dependencies?
There is a use case for creating a minimal, stand-alone version of a particular package, bundling just what it needs into a deployable image, but I can't remember what conclusions have been reached about that. On 1 October 2010 02:36, Lee Fisher <blib...@gmail.com> wrote: > Hi, > > I have a question about CoApp's support of libraries. The intro > video called static libs 'evil', I'd disagree with, with responsible use. > So, with SxS, and the Dyanmic=goodStatic=bad framing, will I be able to > build a project that responsibly uses static libs, and leverage CoApp? > > Thanks. > > _______________________________________________ > Mailing list: https://launchpad.net/~coapp-developers > Post to : coapp-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~coapp-developers > More help : https://help.launchpad.net/ListHelp > _______________________________________________ Mailing list: https://launchpad.net/~coapp-developers Post to : coapp-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~coapp-developers More help : https://help.launchpad.net/ListHelp
