diff options
Diffstat (limited to 'docs/docs/Packaging-System.html')
| -rw-r--r-- | docs/docs/Packaging-System.html | 24 |
1 files changed, 12 insertions, 12 deletions
diff --git a/docs/docs/Packaging-System.html b/docs/docs/Packaging-System.html index 3c4538a..44f539d 100644 --- a/docs/docs/Packaging-System.html +++ b/docs/docs/Packaging-System.html @@ -16,7 +16,7 @@ Licensed under Gnu Free Documentation License. --> <link href="index.html" rel="start" title="Top"> <link href="Package-Manager.html" rel="up" title="Package Manager"> <link href="Rsync-Repositories.html" rel="next" title="Rsync Repositories"> -<link href="cpt_002dbuild.html" rel="prev" title="cpt-build"> +<link href="Editing-the-build-file-during-pre_002dbuild.html" rel="prev" title="Editing the build file during pre-build"> <style type="text/css"> <!-- a.summary-letter {text-decoration: none} @@ -42,10 +42,10 @@ 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="Usage.html" accesskey="p" rel="prev">Usage</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> </p> </div> <hr> -<span id="Packaging-System-1"></span><h3 class="section">2.2 Packaging System</h3> +<span id="Packaging-System-1"></span><h3 class="section">2.4 Packaging System</h3> <p>A package is formed of several files, these are: </p><ul> @@ -64,7 +64,7 @@ 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.2.1 <samp>build</samp></h4> +<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 code to be installed on the target system. Even though we will be assuming that @@ -86,7 +86,7 @@ the build script exits on compilation error. </li><li> System architecture </li></ol> -<span id="sources"></span><h4 class="subsection">2.2.2 <samp>sources</samp></h4> +<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 directory during the build process. Those can be remote sources (such as tarballs), @@ -130,14 +130,14 @@ 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.2.3 <samp>checksums</samp></h4> +<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 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. </p> -<span id="version"></span><h4 class="subsection">2.2.4 <samp>version</samp></h4> +<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 of the package on a space seperated format. The contents of the file should look @@ -157,7 +157,7 @@ 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.2.5 <samp>depends</samp></h4> +<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 can append “make” after a dependency to mark a package is only required during @@ -173,18 +173,18 @@ python test zlib </pre></div> -<span id="post_002dinstall"></span><h4 class="subsection">2.2.6 <samp>post-install</samp></h4> +<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.2.7 <samp>message</samp></h4> +<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.2.8 <samp>test</samp></h4> +<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 will only run if the user has the <code>CPT_TEST</code> variable set, or the build is @@ -194,7 +194,7 @@ build directory. It is run right after the build script is finished. <hr> <div class="header"> <p> -Next: <a href="Rsync-Repositories.html" accesskey="n" rel="next">Rsync Repositories</a>, Previous: <a href="Usage.html" accesskey="p" rel="prev">Usage</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> </p> </div> |