22 Apr
2006
22 Apr
'06
4:25 p.m.
On Sat, Apr 22, 2006 at 09:11:17PM +0100, Steve Harris wrote:
On Sat, Apr 22, 2006 at 08:19:44PM +0200, Lars Luthman
wrote:
Err... and this is so that you can provide plugins individually for
download, eg. for the case where someone downloads a patch that requires
one plugin you dont have, and otherwise it would have onerous requirements.
- Steve
On Sat, 2006-04-22 at 19:12 +0100, Steve Harris
wrote:
Its for when theres a system installed version of the library, but you
want to provide one incase there isn't. E) Bundles: no-one screamed when I suggested it,
but its a bit different to
LADSPA 1's /lib directory. Hosts would be required to allow the plugin
link to libraries in the bundle if they need to (this is why OPENSTEP did
it, I guess its done by setting LD_LIBRARY_PATH, but I dont know), which
is a bit more work, but makes moving plugins between machines easier.
I don't really see the point in storing shared libraries in the bundle.
If you are using your own copy of a library already, why not just link
it statically?