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

Re: Reply to a RFP on the right way

Arno, Steve, thanks you both for the resources and links, it will be very helpful.

I know that packaging a library is not the easiest way to start, but I did the packaging of other stuff in the past for my work (not contributed to Debian :-( ).

I'm starting the development of a program that will use this library, and it would be nice if me and the rest of the devel team won't need to install it from sources :-)

El 10/10/11 01:34, Steve Langasek escribió:
On Sun, Oct 09, 2011 at 02:15:42PM +0200, Arno Töll wrote:

In addition, if you follow the link you will see that the library is
called "jsoncpp". What is the right name I should choose for my package?
I intend that libjsoncpp is appropriate, because I suppose that all the
library packages on Debian are named lib*. Is this true?
Not all zlib1g is a counter example (although that's a very old library
following a naming scheme not used anymore). Libraries have a very
strict naming schema, typically the name is lib<libraryname><soversion.
Please use the following hacky script to determine the correct name of
your library:
  objdump -p /path/to/libfoo-bar.so.1.2.3 | \
   sed -n -e's/^[[:space:]]*SONAME[[:space:]]*//p' | \
   sed -e's/\([0-9]\)\.so\./\1-/; s/\.so\.//'
To clarify: the custom is to use the upstream name for the source package,
and to name the binary package after the library soname.  You don't want to
change the source package name every time the upstream soname changes.

Reply to: