[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Plugin API/ABI versions

On Fri, 2007-06-01 at 18:03 +0200, Magnus Holmgren wrote:
> Many applications allow their functionality to be extended by means of 
> plugins, often in the form of libraries that the application dlopen()s. 
> Usually the application provides an API, and like other APIs these APIs (and 
> ABIs) can evolve, calling for versioned dependencies. But executables aren't 
> shared libraries, so there are no SONAME/NEEDED tags (typically, AFAIK, the 
> API headers define some version constants that the application queries the 
> plugin for to detect incompatibilities) and using dpkg-shlibdeps doesn't 
> work. So how should the -dev package provide correct dependency information 
> in these cases?

The ion3 package provides "ion3-api-" + an API identifier, and
separately-packaged modules depend on this.  The API identifier is in
one of the headers in the -dev package.


Ben Hutchings
The obvious mathematical breakthrough [to break modern encryption] would be
development of an easy way to factor large prime numbers. - Bill Gates

Attachment: signature.asc
Description: This is a digitally signed message part

Reply to: