library name collision when upgrade to slang-v2.0

[vowstar]

Describe the bug

Before I used the source code of v1.0 to compile and install without problems.

Later, when v2.0 was released, I tried to compile and install it with the source code of v2.0, and found that two paths were generated that conflicted with the existing libslang.so of the system:

 * Detected file collision(s):
 *
 * /usr/lib64/libslang.so
 * /usr/lib64/libslang.so.2

To Reproduce

This problem is easy to reproduce on CentOS 7. For example, you can install any package that depends on slang(not this repo), such as newt, libcaca, nettop, util-linux, etc.

Fastest way to reproduce:

yum install slang

Then CentOS 7 will have:

/usr/lib64/libslang.so.2
/usr/lib64/libslang.so.2.2.4

And then download https://github.com/MikePopoloski/slang/releases/tag/v2.0 source code, compile and install:

git clone -b v2.0 https://github.com/MikePopoloski/slang.git
mkdir build && cd build && cmake .. && make -j && make install

Then the two files will conflict, resulting in corruption.

Additional context

Except on CentOS, on other operating systems, library name conflicts will still cause program running errors.

For example debian/ubuntu based OS:

https://packages.debian.org/search?arch=any&mode=filename&searchon=contents&keywords=libslang.so.2

For example:
AlmaLinux 9
AlmaLinux 8
ALT Linux P10
ALT Linux P9
ALT Linux Sisyphus
Amazon Linux 2
Amazon Linux 1
CentOS 9 Stream
CentOS 8 Stream
CentOS 8
CentOS 7
Fedora 36
Fedora 35
Fedora Rawhide
Mageia 8
Mageia Cauldron
OpenMandriva Lx 4.3
OpenMandriva Lx 4.2
OpenMandriva Rolling
OpenMandriva Cooker
openSUSE Leap 15.4
openSUSE Leap 15.3
openSUSE Tumbleweed
PCLinuxOS
Rocky Linux 9
Rocky Linux 8

https://pkgs.org/download/libslang.so.2()(64bit)

Since this name has been taken and is well known, it is de facto unavailable in version v2.0.
v1.0 does not have this name collision problem.

I am trying to make this package for the gentoo distribution, and the test passed in v1.0, and have issue in v2.0.

[MikePopoloski]

Hmm, that's unfortunate. I did not know about this "s-lang" library. Not sure what to do about this... a rename would be pretty painful at this point.

[vowstar]

I temporarily replaced libslang.so with libsvlang.so in my local environment. If the final solution is given in upstream, I will follow the upstream way.

[vowstar]

I work around this issue with static build, but still difficult to package it for linux distribution as a dynamic link library.

[vowstar]

Thanks for #650, I'll be using libsvlang.so for Gentoo Linux packaging.

[MikePopoloski]

This should be fixed now. The default lib name is set to libsvlang