Re: package naming

MoiN On Mon, Feb 12, 2001 at 04:30:32PM +0100, Ove Kaaven wrote: > Are there any docs with guidelines on package naming? See the packaging manual, Section 11.3. > The build process gives me > libmk4.so.0.0.0, libmk4tcl.so.0.0.0, and optionally libmk4py.so.0.0.0 So your package should be called

autoconf macros and C++

I'm writing a program that uses the libapt-pkg library. In my configure.in I wanted to check to see if libapt-pkg.so was installed and gve a warning if it isn't. The way to do this I'm told is to use the AC_CHECK_LIBS macro giving it the name of the library and a function in that library. auto

Re: Packaging unversioned shared libraries

On Wed, Feb 14, 2001 at 06:51:35PM +, Roger Leigh wrote: > I am having a problem when packaging a shared library (libgimpprint from > CVS). It is normally named libgimpprint-.so e.g. currently > libgimpprint-4.1.4.so, but I get errors when packaging (see below). > However, if I change that nam

Packaging unversioned shared libraries

I am having a problem when packaging a shared library (libgimpprint from CVS). It is normally named libgimpprint-.so e.g. currently libgimpprint-4.1.4.so, but I get errors when packaging (see below). However, if I change that naming to libgimpprint.so.4.0.0, I do not get these lintian errors. Is th

Re: Packaging unversioned shared libraries

On Wed, Feb 14, 2001 at 06:51:35PM +, Roger Leigh wrote: > I am having a problem when packaging a shared library (libgimpprint from > CVS). It is normally named libgimpprint-.so e.g. currently > libgimpprint-4.1.4.so, but I get errors when packaging (see below). > However, if I change that na

Packaging unversioned shared libraries

I am having a problem when packaging a shared library (libgimpprint from CVS). It is normally named libgimpprint-.so e.g. currently libgimpprint-4.1.4.so, but I get errors when packaging (see below). However, if I change that naming to libgimpprint.so.4.0.0, I do not get these lintian errors. Is t