> Is this shared library actually used by other programs? Or only > within the internal use of this particular project? If the latter > then I would avoid packaging it as a shared library at all. If the > shared library is not used by other programs then I would covert the > build to link the project library code as an archive library for > Debian. That should avoid most of the problems.
Well the goal is to make it available to other programs, so a shared library is preferable. A -dev package will be available too to allow users to compile binaries and link them against the .so library... ------------------------------------------------- envoyé via Webmail/IMAG ! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
