diff options
| author | Craig Small <csmall@dropbear.xyz> | 2021-02-20 22:30:31 +1100 |
|---|---|---|
| committer | Craig Small <csmall@dropbear.xyz> | 2021-02-20 22:30:31 +1100 |
| commit | 9aa09d8862c00a8dc85910d0365332c8c99b59ce (patch) | |
| tree | c3c2059cd6511423beb07a546311ba0016a058c0 /.gitignore | |
| parent | aaa0cd48b0618dbcba26289d93a3a59a1dc0bdbc (diff) | |
| download | procps-ng-9aa09d8862c00a8dc85910d0365332c8c99b59ce.tar.gz | |
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>
Diffstat (limited to '.gitignore')
| -rw-r--r-- | .gitignore | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -45,8 +45,8 @@ pmap pidwait procps-ng-*.tar.xz proc/.depend -proc/libprocps.la -proc/libprocps.pc +proc/libproc-2.la +proc/libproc-2.pc proc/Makefile proc/Makefile.in ps/Makefile |