Philipp Kern wrote: > `libopm' and the `OPM' Perl module in it could be split out to enable > others to use those components directly (e.g. for Open Proxy scanning > outside of IRC environments).
Actually `libopm' is linked statically into `bopm' in `src/Makefile.am'. But the main problem I see, apart of the extra binary and development packages needed, is the lacking SONAME of `libopm'. Most probably there is no ABI stability guaranteed and we would need to check for API/ABI differences every time a new release comes out. (Which, uh, doesn't happen too often, though.) An alternative could be to export solely the static library in a development package and link dependent packages and programs statically. With `libopm' and the corresponding `OPM' Perl module people could realise background open proxy checks e.g in Web environments. There are the obvious drawbacks of course, the programs are not updated when the library is fixed in any way. Is this way to accomplish the task valid? Are static-only packages still allowed into the archive? Kind regards, Philipp Kern -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
