diff options
Diffstat (limited to 'docs/docs/Packaging-System.html')
| -rw-r--r-- | docs/docs/Packaging-System.html | 29 |
1 files changed, 26 insertions, 3 deletions
diff --git a/docs/docs/Packaging-System.html b/docs/docs/Packaging-System.html index 44f539d..7268068 100644 --- a/docs/docs/Packaging-System.html +++ b/docs/docs/Packaging-System.html @@ -2,7 +2,12 @@ <html> <!-- Copyright (C) 2020 Cem Keylan -Licensed under Gnu Free Documentation License. --> +Permission is granted to copy, distribute and/or modify this document +under the terms of the GNU Free Documentation License, Version 1.3 or +any later version published by the Free Software Foundation; with no +Invariant Sections, with no Front-Cover Texts and no Back-Cover Texts. +A copy of the license is included in the section entitled "GNU Free +Documentation License." --> <!-- Created by GNU Texinfo 6.7, http://www.gnu.org/software/texinfo/ --> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> @@ -14,6 +19,7 @@ Licensed under Gnu Free Documentation License. --> <meta name="distribution" content="global"> <meta name="Generator" content="makeinfo"> <link href="index.html" rel="start" title="Top"> +<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents"> <link href="Package-Manager.html" rel="up" title="Package Manager"> <link href="Rsync-Repositories.html" rel="next" title="Rsync Repositories"> <link href="Editing-the-build-file-during-pre_002dbuild.html" rel="prev" title="Editing the build file during pre-build"> @@ -42,7 +48,7 @@ ul.no-bullet {list-style: none} <body lang="en"> <span id="Packaging-System"></span><div class="header"> <p> -Next: <a href="Rsync-Repositories.html" accesskey="n" rel="next">Rsync Repositories</a>, Previous: <a href="Hooks.html" accesskey="p" rel="prev">Hooks</a>, Up: <a href="Package-Manager.html" accesskey="u" rel="up">Package Manager</a> </p> +Next: <a href="Rsync-Repositories.html" accesskey="n" rel="next">Rsync Repositories</a>, Previous: <a href="Hooks.html" accesskey="p" rel="prev">Hooks</a>, Up: <a href="Package-Manager.html" accesskey="u" rel="up">Package Manager</a> [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>]</p> </div> <hr> <span id="Packaging-System-1"></span><h3 class="section">2.4 Packaging System</h3> @@ -64,6 +70,8 @@ package maintainer. Everything in the package directory will also be added to th package database that is located on ’/var/db/cpt/installed’. These can be patches, configuration files, etc. </p> + + <span id="build"></span><h4 class="subsection">2.4.1 <samp>build</samp></h4> <p>Typically <samp>build</samp> files are shell scripts that run commands to prepare the source @@ -86,6 +94,8 @@ the build script exits on compilation error. </li><li> System architecture </li></ol> + + <span id="sources"></span><h4 class="subsection">2.4.2 <samp>sources</samp></h4> <p><samp>sources</samp> file is a list of files and sources that will be put to the build @@ -130,6 +140,7 @@ history pointer, git will checkout the relevant revision. So, added with their paths relative to the package directory. </p> + <span id="checksums"></span><h4 class="subsection">2.4.3 <samp>checksums</samp></h4> <p>checksums file is generated by the <samp>cpt c pkg command</samp>. It is generated @@ -137,6 +148,8 @@ according to the order of the sources file. That’s why you shouldn’t it manually. The checksums file is created with the digests of the files using the sha256 algorithm. </p> + + <span id="version"></span><h4 class="subsection">2.4.4 <samp>version</samp></h4> <p>The version file includes the version of the software and the release number of @@ -157,6 +170,8 @@ drastic changes that require a rebuild Those can be, <p>When a version bump occurs, the release should be reset to 1. </p> + + <span id="depends"></span><h4 class="subsection">2.4.5 <samp>depends</samp></h4> <p>This is a list of dependencies that must be installed before a package build. You @@ -173,17 +188,23 @@ python test zlib </pre></div> + + <span id="post_002dinstall"></span><h4 class="subsection">2.4.6 <samp>post-install</samp></h4> <p><samp>post-install</samp> files 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 <code>CPT_ROOT</code>). </p> + + <span id="message"></span><h4 class="subsection">2.4.7 <samp>message</samp></h4> <p>This plaintext file will be outputted with <code>cat</code> after every package is installed. </p> + + <span id="test"></span><h4 class="subsection">2.4.8 <samp>test</samp></h4> <p>Test files are mainly for the repository maintainer to test the packages, and @@ -191,10 +212,12 @@ will only run if the user has the <code>CPT_TEST</code> variable set, or the bui run with the <samp>-t</samp> or <samp>--test</samp> options. This script is run on the build directory. It is run right after the build script is finished. </p> + + <hr> <div class="header"> <p> -Next: <a href="Rsync-Repositories.html" accesskey="n" rel="next">Rsync Repositories</a>, Previous: <a href="Hooks.html" accesskey="p" rel="prev">Hooks</a>, Up: <a href="Package-Manager.html" accesskey="u" rel="up">Package Manager</a> </p> +Next: <a href="Rsync-Repositories.html" accesskey="n" rel="next">Rsync Repositories</a>, Previous: <a href="Hooks.html" accesskey="p" rel="prev">Hooks</a>, Up: <a href="Package-Manager.html" accesskey="u" rel="up">Package Manager</a> [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>]</p> </div> |