cpt

[ARCHIVED] Carbs Packaging Tools
git clone git://git.ckyln.com/~cem/cpt.git
Log | Files | Refs | README | LICENSE

commit 8c28a113881dc55924bcabbb6205d762386e43c4
parent 7734e6a326ad7543c8c140355b4e20ff116db356
Author: Cem Keylan <cem@ckyln.com>
Date:   Fri, 24 Jul 2020 14:32:15 +0300

doc: change command names and documents

Diffstat:
Mdoc/package-system.txt | 12++++++------
Mdoc/rsync-repositories.txt | 2+-
2 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/doc/package-system.txt b/doc/package-system.txt @@ -2,9 +2,9 @@ PACKAGE SYSTEM ================================================================================= -This document talks about the packaging system works with the kiss package -manager in detail. For information regarding the usage of the package manager -itself, see the kiss(1) manual page. +This document talks about the packaging system works with the Carbs Packaging +Tools in detail. For information regarding the usage of the package manager +itself, see the cpt(1) manual page. A package is formed of 4 MANDATORY files. These are, - BUILD @@ -19,7 +19,7 @@ The package manager also reacts to the existence of these files, Any other file can be added to the package directory at the discretion of the package maintainer. Everything in the package directory will also be added to the -package database that is located on '/var/db/kiss/installed'. These can be +package database that is located on '/var/db/cpt/installed'. These can be patches, configuration files, etc. @@ -118,7 +118,7 @@ a source to be on a specific directory, you can see the gcc package for that. CHECKSUMS --------------------------------------------------------------------------------- -checksums file is generated by the `kiss c pkg` command. It is generated +checksums file is generated by the `cpt c pkg` command. It is generated according to the order of the sources file. That's why you shouldn't be editing it manually. The checksums file is created with the digests of the files using the sha256 algorithm. @@ -156,7 +156,7 @@ POST-INSTALL post-installs have the same requirements as the build script. They will be run after the package is installed as root (or as the user if the user has write -permissions on KISS_ROOT). +permissions on CPT_ROOT). MESSAGE diff --git a/doc/rsync-repositories.txt b/doc/rsync-repositories.txt @@ -100,4 +100,4 @@ It is considerably easy to switch to the Carbs Linux rsync repository. +--------------------------------------------------------------------------+ This will fetch the repository to the given location, you can then add it to your -$KISS_PATH. +$CPT_PATH.