Unnecessary(?) SONAME change

[thesamesam]

Commit cd888d8 changed SONAME but at a quick check, it doesn't seem like this was necessary. This breaks compatibility with applications already linked against older libnids and forces them to be rebuilt.

Did the ABI of libnids actually change since the last release or was the SONAME just accidentally changed (here)?

[malwarefrank]

I would actually prefer the SONAME to be minor-version agnostic rather than how it is now. Then the agnostic filename can be a symlink to the latest version-specific file. This is how other libraries are handled on some distributions. I see that the Ubuntu libnids package also has a version-specific name, but different than the one you reference.

I created a branch that looks for the SONAME environment variable at build time and uses that value for the SONAME, which would allow you to easily name it whatever you want, Ubuntu to name it their own way, but also have a sensible default (major-version specific but minor-version agnostic). Take a look at the branch and let me know what you think before I merge it into master and tag it as a new patch-level version.

[malwarefrank]

@thesamesam thoughts on using an ENV var to set soname at build time?