]> granicus.if.org Git - procps-ng/commit
library: Rename to libproc-2
authorCraig Small <csmall@dropbear.xyz>
Sat, 20 Feb 2021 11:30:31 +0000 (22:30 +1100)
committerCraig Small <csmall@dropbear.xyz>
Sat, 20 Feb 2021 11:30:31 +0000 (22:30 +1100)
commit9aa09d8862c00a8dc85910d0365332c8c99b59ce
treec3c2059cd6511423beb07a546311ba0016a058c0
parentaaa0cd48b0618dbcba26289d93a3a59a1dc0bdbc
library: Rename to libproc-2

What to call the new library?

Keep using libprocps wouldn't do, its a very different library from
the programs' point of view. It would also mean we could have some
clashes around the packages (two package names, same library name).

The ancient procps used libproc or libproc-a.b.c where a.b.c was the
package version. Kept the revision numbers down (it was always 0.0.0)
but the name of the library changed.

So if we use libproc-2 is there a clash with an ancient procps?
procps v 2.0.0 was around in 1999 so it was 22 years ago, also the
name of the library would have been libproc-2.0.0.so not libproc-2.so
so we're fine with that.

libproc-2 seems to fit, our second major re-work of the procps
library.

Signed-off-by: Craig Small <csmall@dropbear.xyz>
.gitignore
Makefile.am
NEWS
configure.ac
doc/procps.3
proc/libproc-2.pc.in [moved from proc/libprocps.pc.in with 82% similarity]
proc/libproc-2.sym [moved from proc/libprocps.sym with 98% similarity]