If you're packaging a new library, let's call it foo, keep the development package name "foo_dev", not "foo1_dev" (or any other number).
Good: libfoo1 and foo_dev Not good: libfoo1 and foo1_dev Why? Because as API of the shared library changes, the development package will likely stay the same. You'll end up with libfoo2 and corresponding libfoo1_dev. An exception could be when multiple versions of the development package can coexist, e.g. when they use versioned file names such as /opt/csw/include/foo-1.h. Maciej
