cpt

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

commit e9ed173ee76f8ad4a181495f5d71090bfdbd1520
parent 819895443f787dccbd9b47b5e7468d0ddcfb825d
Author: Cem Keylan <cem@ckyln.com>
Date:   Thu, 16 Jul 2020 13:35:12 +0300

update README

Diffstat:
MREADME.md | 25++++++++++++++-----------
1 file changed, 14 insertions(+), 11 deletions(-)

diff --git a/README.md b/README.md @@ -1,24 +1,26 @@ KISS PACKAGE MANAGER --------------------- +================================================================================ -Package manager for Carbs Linux. Forked from [KISS]. All -usage information can be obtained from the manual page. -For changes please refer to the `CHANGELOG.md` file. +Package manager for Carbs Linux. Forked from [KISS]. All usage information can +be obtained from the manual page. For changes please refer to the `CHANGELOG.md` +file. [KISS]: https://github.com/kisslinux/kiss + Fork Notes ----------- +-------------------------------------------------------------------------------- -There are certain differences between KISS Linux `kiss` and -Carbs Linux `kiss`. Most importantly, you need a C compiler -and a C library (musl/bsd libc) to build this implementation -of it. Rest of the important changes can be found in the CHANGELOG. +There are certain differences between KISS Linux `kiss` and Carbs Linux `kiss`. +Most importantly, you need a C compiler and a C library (musl/bsd libc) to build +this implementation of it. Rest of the important changes can be found in the +CHANGELOG. This is _mostly_ a shell implementation rather than a pure one. + Directory Structure -------------------- +-------------------------------------------------------------------------------- / -- kiss, README, Makefile, LICENSE, CHANGELOG bin/ -- for C programs. @@ -26,8 +28,9 @@ Directory Structure doc/ -- for documentation. contrib/ -- for Shell scripts that wrap around kiss. + Contributing ------------- +-------------------------------------------------------------------------------- Please see the [style and contribution guidelines].