Kpum is a user management software designed specifically for the pureftpd server, making it easier to manage users and their permissions.
Kpum is a user management software specifically designed for the pureftpd server, which allows users to add, modify or delete existing users on the server. The software currently offers support for the pureftpd.pdb database and operates as an application on KDE environments.
The installation process of Kpum begins with the `configure' shell script that attempts to identify the various system-dependent variables required during the compilation. This script uses those values to generate a `Makefile' in every directory within the package. It may also create one or more `.h' files incorporating system-dependent definitions. Finally, the shell script creates a `config.status' file that users can run in the future to recreate the present configuration, a `config.cache' file that saves the results of the tests to speed up reconfiguring, and a `config.log' file containing compiler output which is mainly useful for debugging `configure'.
The software allows users to perform unusual configurations while compiling the package. However, users must figure out how `configure' would check whether to perform them or not and send diffs, or instructions to the provided address given in the `README', so they may be considered for the next software release. If `config.cache' contains results users do not need, they may edit or remove it.
Kpum uses `configure.in' to create `configure' through a program referred to as `autoconf'. Users only need `configure.in' if they want to change it or regenerate `configure' using a newer version of the `autoconf' program.
To compile the package, the simplest process is to `cd' to the directory containing the source code for the package and type `./configure' followed by `make' to compile the package. Users can optionally type `make check' to run any self-tests that come with the package. Once completed, they can install the programs and any data files and documentation by typing `make install.' Users can then remove the program binaries and object files from the source code directory by typing `make clean.' To remove the files that `configure' created and to compile the package for a different type of computer, users can type `make distclean.' For the package's developers, there exists a `make maintainer-clean' target. However, if they use it, they may need to obtain other programs to regenerate files that came with the distribution.
The installation process of Kpum begins with the `configure' shell script that attempts to identify the various system-dependent variables required during the compilation. This script uses those values to generate a `Makefile' in every directory within the package. It may also create one or more `.h' files incorporating system-dependent definitions. Finally, the shell script creates a `config.status' file that users can run in the future to recreate the present configuration, a `config.cache' file that saves the results of the tests to speed up reconfiguring, and a `config.log' file containing compiler output which is mainly useful for debugging `configure'.
The software allows users to perform unusual configurations while compiling the package. However, users must figure out how `configure' would check whether to perform them or not and send diffs, or instructions to the provided address given in the `README', so they may be considered for the next software release. If `config.cache' contains results users do not need, they may edit or remove it.
Kpum uses `configure.in' to create `configure' through a program referred to as `autoconf'. Users only need `configure.in' if they want to change it or regenerate `configure' using a newer version of the `autoconf' program.
To compile the package, the simplest process is to `cd' to the directory containing the source code for the package and type `./configure' followed by `make' to compile the package. Users can optionally type `make check' to run any self-tests that come with the package. Once completed, they can install the programs and any data files and documentation by typing `make install.' Users can then remove the program binaries and object files from the source code directory by typing `make clean.' To remove the files that `configure' created and to compile the package for a different type of computer, users can type `make distclean.' For the package's developers, there exists a `make maintainer-clean' target. However, if they use it, they may need to obtain other programs to regenerate files that came with the distribution.
What's New
Version 0.5.3.1: N/A