Home Explore Help
Sign In
bkmgit
/
dragora
forked from dragora/dragora
Watch 1
Star 0
Fork 0
Files
Branch: master
Branches Tags
dragora
/
qi
/
doc
/
qi.html

qi.html 61 KB
Permalink History Raw

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850851852853854855856857858859860861862863864865866867868869870871872873874875876877878879880881882883884885886887888889890891892893894895896897898899900901902903904905906907908909910911912913914915916917918919920921922923924925926927928929930931932933934935936937938939940941942943944945946947948949950951952953954955956957958959960961962963964965966967968969970971972973974975976977978979980981982983984985986987988989990991992993994995996997998999100010011002100310041005100610071008100910101011101210131014101510161017101810191020102110221023102410251026102710281029103010311032103310341035103610371038103910401041104210431044104510461047104810491050105110521053105410551056105710581059106010611062106310641065106610671068106910701071107210731074107510761077107810791080108110821083108410851086108710881089109010911092109310941095109610971098109911001101110211031104110511061107110811091110111111121113111411151116111711181119112011211122112311241125112611271128112911301131113211331134113511361137113811391140114111421143114411451146114711481149115011511152115311541155115611571158115911601161116211631164116511661167116811691170117111721173117411751176117711781179118011811182118311841185118611871188118911901191119211931194119511961197119811991200120112021203120412051206120712081209121012111212121312141215121612171218121912201221122212231224122512261227122812291230123112321233123412351236123712381239124012411242124312441245124612471248124912501251125212531254125512561257125812591260126112621263126412651266126712681269127012711272127312741275127612771278127912801281128212831284128512861287128812891290129112921293129412951296129712981299130013011302130313041305130613071308130913101311131213131314131513161317131813191320132113221323132413251326132713281329133013311332133313341335133613371338133913401341134213431344134513461347134813491350135113521353135413551356135713581359136013611362136313641365136613671368136913701371137213731374137513761377137813791380138113821383138413851386138713881389139013911392139313941395139613971398139914001401140214031404140514061407140814091410141114121413141414151416141714181419142014211422142314241425142614271428142914301431143214331434143514361437143814391440144114421443144414451446144714481449145014511452145314541455145614571458145914601461146214631464146514661467 
  1. <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
    2. 

  2. <html>
    3. 

  3. <!-- Copyright (C) 2019-2023 Matias Andres Fonzo, Santiago del Estero,
    4. 

  4. Argentina.
    5. 

  5. 

  6. Permission is granted to copy, distribute and/or modify this document
    7. 

  7. under the terms of the GNU Free Documentation License, Version 1.3 or
    8. 

  8. any later version published by the Free Software Foundation; with no
    9. 

  9. Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. -->
    10. 

  10. <!-- Created by GNU Texinfo 6.7, http://www.gnu.org/software/texinfo/ -->
    11. 

  11. <head>
    12. 

  12. <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
    13. 

  13. <title>Qi user guide</title>
    14. 

  14. 

  15. <meta name="description" content="Qi user guide">
    16. 

  16. <meta name="keywords" content="Qi user guide">
    17. 

  17. <meta name="resource-type" content="document">
    18. 

  18. <meta name="distribution" content="global">
    19. 

  19. <meta name="Generator" content="makeinfo">
    20. 

  20. <link href="#Top" rel="start" title="Top">
    21. 

  21. <link href="#Index" rel="index" title="Index">
    22. 

  22. <style type="text/css">
    23. 

  23. <!--
    24. 

  24. a.summary-letter {text-decoration: none}
    25. 

  25. blockquote.indentedblock {margin-right: 0em}
    26. 

  26. div.display {margin-left: 3.2em}
    27. 

  27. div.example {margin-left: 3.2em}
    28. 

  28. div.lisp {margin-left: 3.2em}
    29. 

  29. kbd {font-style: oblique}
    30. 

  30. pre.display {font-family: inherit}
    31. 

  31. pre.format {font-family: inherit}
    32. 

  32. pre.menu-comment {font-family: serif}
    33. 

  33. pre.menu-preformatted {font-family: serif}
    34. 

  34. span.nolinebreak {white-space: nowrap}
    35. 

  35. span.roman {font-family: initial; font-weight: normal}
    36. 

  36. span.sansserif {font-family: sans-serif; font-weight: normal}
    37. 

  37. ul.no-bullet {list-style: none}
    38. 

  38. -->
    39. 

  39. </style>
    40. 

  40. 

  41. 

  42. </head>
    43. 

  43. 

  44. <body lang="en">
    45. 

  45. <h1 class="settitle" align="center">Qi user guide</h1>
    46. 

  46. 

  47. 

  48. 

  49. 

  50. 

  51. <span id="Top"></span><div class="header">
    52. 

  52. <p>
    53. 

  53. Next: <a href="#Introduction-to-Qi" accesskey="n" rel="next">Introduction to Qi</a> &nbsp; [<a href="#Index" title="Index" rel="index">Index</a>]</p>
    54. 

  54. </div>
    55. 

  55. <span id="SEC_Top"></span>
    56. 

  56. <p>This user guide is for Qi (version 2.12-rc2,
    57. 

  57. 11 Apr 2023).
    58. 

  58. </p>
    59. 

  59. <table class="menu" border="0" cellspacing="0">
    60. 

  60. <tr><td align="left" valign="top">&bull; <a href="#Introduction-to-Qi" accesskey="1">Introduction to Qi</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">Description and features of qi
    61. 

  61. </td></tr>
    62. 

  62. <tr><td align="left" valign="top">&bull; <a href="#Invoking-qi" accesskey="2">Invoking qi</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">Command-line options
    63. 

  63. </td></tr>
    64. 

  64. <tr><td align="left" valign="top">&bull; <a href="#The-qirc-file" accesskey="3">The qirc file</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">Configuration file
    65. 

  65. </td></tr>
    66. 

  66. <tr><td align="left" valign="top">&bull; <a href="#Packages" accesskey="4">Packages</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">Managing packages
    67. 

  67. </td></tr>
    68. 

  68. <tr><td align="left" valign="top">&bull; <a href="#Recipes" accesskey="5">Recipes</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">Building packages
    69. 

  69. </td></tr>
    70. 

  70. <tr><td align="left" valign="top">&bull; <a href="#Order-files" accesskey="6">Order files</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">Handling build order
    71. 

  71. </td></tr>
    72. 

  72. <tr><td align="left" valign="top">&bull; <a href="#Creating-packages" accesskey="7">Creating packages</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">Making Qi packages
    73. 

  73. </td></tr>
    74. 

  74. <tr><td align="left" valign="top">&bull; <a href="#Examining-packages" accesskey="8">Examining packages</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">Debugging purposes
    75. 

  75. </td></tr>
    76. 

  76. <tr><td align="left" valign="top">&bull; <a href="#Qi-exit-status" accesskey="9">Qi exit status</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">Exit codes
    77. 

  77. </td></tr>
    78. 

  78. <tr><td align="left" valign="top">&bull; <a href="#Index" rel="index">Index</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
    79. 

  79. </td></tr>
    80. 

  80. </table>
    81. 

  81. 

  82. <br>
    83. 

  83. <p>Copyright &copy; 2019-2023 Matias Andres Fonzo, Santiago del Estero,
    84. 

  84. Argentina.
    85. 

  85. </p>
    86. 

  86. <p>Permission is granted to copy, distribute and/or modify this document
    87. 

  87. under the terms of the GNU Free Documentation License, Version 1.3 or
    88. 

  88. any later version published by the Free Software Foundation; with no
    89. 

  89. Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
    90. 

  90. </p>
    91. 

  91. 

  92. <hr>
    93. 

  93. <span id="Introduction-to-Qi"></span><div class="header">
    94. 

  94. <p>
    95. 

  95. Next: <a href="#Invoking-qi" accesskey="n" rel="next">Invoking qi</a>, Previous: <a href="#Top" accesskey="p" rel="prev">Top</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Index" title="Index" rel="index">Index</a>]</p>
    96. 

  96. </div>
    97. 

  97. <span id="Introduction-to-Qi-1"></span><h2 class="chapter">1 Introduction to Qi</h2>
    98. 

  98. <span id="index-introduction-to-qi"></span>
    99. 

  99. 

  100. <p>Qi is a simple but well-integrated package manager.  It can create,
    101. 

  101. install, remove, and upgrade software packages.  Qi produces binary
    102. 

  102. packages using recipes, which are files containing specific instructions
    103. 

  103. to build each package from source.  Qi can manage multiple packages
    104. 

  104. under a single directory hierarchy.  This method allows to maintain a set
    105. 

  105. of packages and multiple versions of them.  This means that Qi could be
    106. 

  106. used as the main package manager or complement the existing one.
    107. 

  107. </p>
    108. 

  108. <p>Qi offers a friendly command line interface, a global configuration
    109. 

  109. file, a simple recipe layout to deploy software packages; also works
    110. 

  110. with binary packages in parallel, speeding up installations and packages
    111. 

  111. in production.  The format used for packages is a simplified and safer
    112. 

  112. variant of POSIX pax archive compressed in lzip format.
    113. 

  113. </p>
    114. 

  114. <p>Qi is a modern (POSIX-compliant) shell script released under the
    115. 

  115. terms of the GNU General Public License.  There are only two major
    116. 

  116. dependencies for the magic: graft(1) and tarlz(1), the rest is expected
    117. 

  117. to be found in any Unix-like system.
    118. 

  118. </p>
    119. 

  119. <hr>
    120. 

  120. <span id="Invoking-qi"></span><div class="header">
    121. 

  121. <p>
    122. 

  122. Next: <a href="#The-qirc-file" accesskey="n" rel="next">The qirc file</a>, Previous: <a href="#Introduction-to-Qi" accesskey="p" rel="prev">Introduction to Qi</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Index" title="Index" rel="index">Index</a>]</p>
    123. 

  123. </div>
    124. 

  124. <span id="Invoking-qi-1"></span><h2 class="chapter">2 Invoking qi</h2>
    125. 

  125. <span id="index-invocation"></span>
    126. 

  126. 

  127. <p>This chapter describes the synopsis for invoking Qi.
    128. 

  128. </p>
    129. 

  129. <div class="example">
    130. 

  130. <pre class="example">Usage: qi COMMAND [<var>OPTION</var>...] [<var>FILE</var>]...
    131. 

  131. </pre></div>
    132. 

  132. 

  133. <p>One mandatory command specifies the operation that &lsquo;<samp>qi</samp>&rsquo; should
    134. 

  134. perform, options are meant to detail how this operation should be
    135. 

  135. performed during or after the process.
    136. 

  136. </p>
    137. 

  137. <p>Qi supports the following commands:
    138. 

  138. </p>
    139. 

  139. <dl compact="compact">
    140. 

  140. <dt><code>warn</code></dt>
    141. 

  141. <dd><p>Warn about files that will be installed.
    142. 

  142. </p>
    143. 

  143. </dd>
    144. 

  144. <dt><code>install</code></dt>
    145. 

  145. <dd><p>Install packages.
    146. 

  146. </p>
    147. 

  147. </dd>
    148. 

  148. <dt><code>remove</code></dt>
    149. 

  149. <dd><p>Remove packages.
    150. 

  150. </p>
    151. 

  151. </dd>
    152. 

  152. <dt><code>upgrade</code></dt>
    153. 

  153. <dd><p>Upgrade packages.
    154. 

  154. </p>
    155. 

  155. </dd>
    156. 

  156. <dt><code>extract</code></dt>
    157. 

  157. <dd><p>Extract packages for debugging purposes.
    158. 

  158. </p>
    159. 

  159. </dd>
    160. 

  160. <dt><code>create</code></dt>
    161. 

  161. <dd><p>Create a .tlz package from directory.
    162. 

  162. </p>
    163. 

  163. </dd>
    164. 

  164. <dt><code>build</code></dt>
    165. 

  165. <dd><p>Build packages using recipe names.
    166. 

  166. </p>
    167. 

  167. </dd>
    168. 

  168. <dt><code>order</code></dt>
    169. 

  169. <dd><p>Resolve build order through .order files
    170. 

  170. </p></dd>
    171. 

  171. </dl>
    172. 

  172. 

  173. <p>Options when installing, removing, or upgrading software packages:
    174. 

  174. </p>
    175. 

  175. <dl compact="compact">
    176. 

  176. <dt><code>-f</code></dt>
    177. 

  177. <dt><code>--force</code></dt>
    178. 

  178. <dd><p>Force upgrade of pre-existing packages.
    179. 

  179. </p>
    180. 

  180. </dd>
    181. 

  181. <dt><code>-k</code></dt>
    182. 

  182. <dt><code>--keep</code></dt>
    183. 

  183. <dd><p>Keep directories when build/remove/upgrade.
    184. 

  184. </p>
    185. 

  185. <p>Keep (don&rsquo;t delete) the package directory when using remove/upgrade command.
    186. 

  186. </p>
    187. 

  187. <p>This will also try to preserve the directories &lsquo;<samp>${srcdir}</samp>&rsquo; and
    188. 

  188. &lsquo;<samp>${destdir}</samp>&rsquo; when using build command.  Its effect is available in
    189. 

  189. recipes as &lsquo;<samp>${keep_srcdir}</samp>&rsquo; and &lsquo;<samp>${keep_destdir}</samp>&rsquo;.  See
    190. 

  190. <a href="#Recipes">Special variables</a> for details.
    191. 

  191. </p>
    192. 

  192. </dd>
    193. 

  193. <dt><code>-p</code></dt>
    194. 

  194. <dt><code>--prune</code></dt>
    195. 

  195. <dd><p>Prune conflicts.
    196. 

  196. </p>
    197. 

  197. </dd>
    198. 

  198. <dt><code>-P</code></dt>
    199. 

  199. <dt><code>--packagedir=&lt;dir&gt;</code></dt>
    200. 

  200. <dd><p>Set directory for package installations.
    201. 

  201. </p>
    202. 

  202. </dd>
    203. 

  203. <dt><code>-t</code></dt>
    204. 

  204. <dt><code>--targetdir=&lt;dir&gt;</code></dt>
    205. 

  205. <dd><p>Set target directory for symbolic links.
    206. 

  206. </p>
    207. 

  207. </dd>
    208. 

  208. <dt><code>-r</code></dt>
    209. 

  209. <dt><code>--rootdir=&lt;dir&gt;</code></dt>
    210. 

  210. <dd><p>Use the fully qualified named directory as the root directory for all qi
    211. 

  211. operations.
    212. 

  212. </p>
    213. 

  213. <p>Note: the target directory and the package directory will be
    214. 

  214. relative to the specified directory, excepting the graft log file.
    215. 

  215. </p></dd>
    216. 

  216. </dl>
    217. 

  217. 

  218. <p>Options when building software packages using recipes:
    219. 

  219. </p>
    220. 

  220. <dl compact="compact">
    221. 

  221. <dt><code>-a</code></dt>
    222. 

  222. <dt><code>--architecture</code></dt>
    223. 

  223. <dd><p>Set architecture name for the package.
    224. 

  224. </p>
    225. 

  225. </dd>
    226. 

  226. <dt><code>-j</code></dt>
    227. 

  227. <dt><code>--jobs</code></dt>
    228. 

  228. <dd><p>Parallel jobs for the compiler.
    229. 

  229. </p>
    230. 

  230. <p>This option sets the variable &lsquo;<samp>${jobs}</samp>&rsquo;.  If not specified, default
    231. 

  231. sets to 1.
    232. 

  232. </p>
    233. 

  233. </dd>
    234. 

  234. <dt><code>-S</code></dt>
    235. 

  235. <dt><code>--skip-questions</code></dt>
    236. 

  236. <dd><p>Skip questions on completed recipes.
    237. 

  237. </p>
    238. 

  238. </dd>
    239. 

  239. <dt><code>-1</code></dt>
    240. 

  240. <dt><code>--increment</code></dt>
    241. 

  241. <dd><p>Increment release number (&lsquo;<samp>${release}</samp>&rsquo; + 1).
    242. 

  242. </p>
    243. 

  243. <p>The effect of this option will be omitted if &ndash;no-package is being used.
    244. 

  244. </p>
    245. 

  245. </dd>
    246. 

  246. <dt><code>-n</code></dt>
    247. 

  247. <dt><code>--no-package</code></dt>
    248. 

  248. <dd><p>Do not create a .tlz package.
    249. 

  249. </p>
    250. 

  250. </dd>
    251. 

  251. <dt><code>-i</code></dt>
    252. 

  252. <dt><code>--install</code></dt>
    253. 

  253. <dd><p>Install package after the build.
    254. 

  254. </p>
    255. 

  255. </dd>
    256. 

  256. <dt><code>-u</code></dt>
    257. 

  257. <dt><code>--upgrade</code></dt>
    258. 

  258. <dd><p>Upgrade package after the build.
    259. 

  259. </p>
    260. 

  260. </dd>
    261. 

  261. <dt><code>-o</code></dt>
    262. 

  262. <dt><code>--outdir=&lt;dir&gt;</code></dt>
    263. 

  263. <dd><p>Where the packages produced will be written.
    264. 

  264. </p>
    265. 

  265. <p>This option sets the variable &lsquo;<samp>${outdir}</samp>&rsquo;.
    266. 

  266. </p>
    267. 

  267. </dd>
    268. 

  268. <dt><code>-w</code></dt>
    269. 

  269. <dt><code>--worktree=&lt;dir&gt;</code></dt>
    270. 

  270. <dd><p>Where archives, patches, recipes are expected.
    271. 

  271. </p>
    272. 

  272. <p>This option sets the variable &lsquo;<samp>${worktree}</samp>&rsquo;.
    273. 

  273. </p>
    274. 

  274. </dd>
    275. 

  275. <dt><code>-s</code></dt>
    276. 

  276. <dt><code>--sourcedir=&lt;dir&gt;</code></dt>
    277. 

  277. <dd><p>Where compressed sources will be found.
    278. 

  278. </p>
    279. 

  279. <p>This option sets the variable &lsquo;<samp>${tardir}</samp>&rsquo;.
    280. 

  280. </p></dd>
    281. 

  281. </dl>
    282. 

  282. 

  283. <p>Other options:
    284. 

  284. </p>
    285. 

  285. <dl compact="compact">
    286. 

  286. <dt><code>-v</code></dt>
    287. 

  287. <dt><code>--verbose</code></dt>
    288. 

  288. <dd><p>Be verbose (an extra -v gives more).
    289. 

  289. </p>
    290. 

  290. <p>It sets the verbosity level, default sets to 0.
    291. 

  291. </p>
    292. 

  292. <p>The value 1 is used for more verbosity while the value 2 is too detailed.
    293. 

  293. Although at the moment it is limited to graft(1) verbosity.
    294. 

  294. </p>
    295. 

  295. </dd>
    296. 

  296. <dt><code>-N</code></dt>
    297. 

  297. <dt><code>--no-rc</code></dt>
    298. 

  298. <dd><p>Do not read the configuration file.
    299. 

  299. </p>
    300. 

  300. <p>This will ignore reading the qirc file.
    301. 

  301. </p>
    302. 

  302. </dd>
    303. 

  303. <dt><code>-L</code></dt>
    304. 

  304. <dt><code>--show-location</code></dt>
    305. 

  305. <dd><p>Print default directory locations and exit.
    306. 

  306. </p>
    307. 

  307. <p>This will print the target directory, package directory, working tree,
    308. 

  308. the directory for sources, and the output directory for the packages
    309. 

  309. produced.  The output will appear on STDOUT as follows:
    310. 

  310. </p>
    311. 

  311. <div class="example">
    312. 

  312. <pre class="example">QI_TARGETDIR=/usr/local
    313. 

  313. QI_PACKAGEDIR=/usr/local/pkgs
    314. 

  314. QI_WORKTREE=/usr/src/qi
    315. 

  315. QI_TARDIR=/usr/src/qi/sources
    316. 

  316. QI_OUTDIR=/var/cache/qi/packages
    317. 

  317. </pre></div>
    318. 

  318. 

  319. <p>You can set these environment variables using one of the following methods:
    320. 

  320. </p>
    321. 

  321. <p><code>eval &quot;$(qi -L)&quot;</code>
    322. 

  322. </p>
    323. 

  323. <p>This will display the default locations taking into account the values set
    324. 

  324. from the qirc configuration file.  You can deny the influence of the
    325. 

  325. configuration file by setting the option &lsquo;<samp>-N</samp>&rsquo;.
    326. 

  326. </p>
    327. 

  327. <p><code>eval &quot;$(qi -N -L)&quot;</code>
    328. 

  328. </p>
    329. 

  329. <p>Or you can adjust the new locations using the command-line options, e.g:
    330. 

  330. </p>
    331. 

  331. <p><code>eval &quot;$(qi -N --targetdir=/directory -L)&quot;</code>
    332. 

  332. </p>
    333. 

  333. </dd>
    334. 

  334. <dt><code>-h</code></dt>
    335. 

  335. <dt><code>--help</code></dt>
    336. 

  336. <dd><p>Display the usage and exit.
    337. 

  337. </p>
    338. 

  338. </dd>
    339. 

  339. <dt><code>-V</code></dt>
    340. 

  340. <dt><code>--version</code></dt>
    341. 

  341. <dd>
    342. 

  342. <p>This will print the (short) version information and then exit.
    343. 

  343. </p>
    344. 

  344. <p>The same can be achieved if Qi is invoked as &lsquo;<samp>qi version</samp>&rsquo;.
    345. 

  345. </p></dd>
    346. 

  346. </dl>
    347. 

  347. 

  348. <p>When FILE is -, qi can read from the standard input.  See examples from
    349. 

  349. the <a href="#Packages">Packages</a> section.
    350. 

  350. </p>
    351. 

  351. <p>Exit status: 0 for a normal exit, 1 for minor common errors (help usage,
    352. 

  352. support not available, etc), 2 to indicate a command execution error;
    353. 

  353. 3 for integrity check error on compressed files, 4 for empty, not
    354. 

  354. regular, or expected files, 5 for empty or not defined variables,
    355. 

  355. 6 when a package already exist, 10 for network manager errors.
    356. 

  356. For more details, see the <a href="#Qi-exit-status">Qi exit status</a> section.
    357. 

  357. </p>
    358. 

  358. 

  359. <hr>
    360. 

  360. <span id="The-qirc-file"></span><div class="header">
    361. 

  361. <p>
    362. 

  362. Next: <a href="#Packages" accesskey="n" rel="next">Packages</a>, Previous: <a href="#Invoking-qi" accesskey="p" rel="prev">Invoking qi</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Index" title="Index" rel="index">Index</a>]</p>
    363. 

  363. </div>
    364. 

  364. <span id="The-qirc-file-1"></span><h2 class="chapter">3 The qirc file</h2>
    365. 

  365. <span id="index-configuration-file"></span>
    366. 

  366. 

  367. <p>The global <samp>qirc</samp> file offers a way to define variables and tools
    368. 

  368. (such as a download manager) for default use.  This file is used by qi
    369. 

  369. at runtime, e.g., to build, install, remove or upgrade packages.
    370. 

  370. </p>
    371. 

  371. <p>Variables and their possible values must be declared as any other
    372. 

  372. variable in the shell.
    373. 

  373. </p>
    374. 

  374. <p>The command line options related to the package directory and target
    375. 

  375. directory and some of the command line options used for the build command,
    376. 

  376. have the power to override the values declared on <samp>qirc</samp>.
    377. 

  377. See <a href="#Invoking-qi">Invoking qi</a>.
    378. 

  378. </p>
    379. 

  379. <p>The order in which qi looks for this file is:
    380. 

  380. </p>
    381. 

  381. <ol>
    382. 

  382. <li> <code>${HOME}/.qirc</code>
    383. 

  383.  Effective user.
    384. 

  384. 

  385. </li><li> &lsquo;<samp>${sysconfdir}/qirc</samp>&rsquo;
    386. 

  386.  System-wide.
    387. 

  387. </li></ol>
    388. 

  388. 

  389. <p>If you intend to run qi as effective user, the file
    390. 

  390. &lsquo;<samp>${sysconfdir}/qirc</samp>&rsquo; could be copied to <code>${HOME}/.qirc</code>
    391. 

  391. setting the paths for &lsquo;<samp>${packagedir}</samp>&rsquo; and &lsquo;<samp>${targetdir}</samp>&rsquo;
    392. 

  392. according to the <code>$HOME</code>.
    393. 

  393. </p>
    394. 

  394. 

  395. <hr>
    396. 

  396. <span id="Packages"></span><div class="header">
    397. 

  397. <p>
    398. 

  398. Next: <a href="#Recipes" accesskey="n" rel="next">Recipes</a>, Previous: <a href="#The-qirc-file" accesskey="p" rel="prev">The qirc file</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Index" title="Index" rel="index">Index</a>]</p>
    399. 

  399. </div>
    400. 

  400. <span id="Packages-1"></span><h2 class="chapter">4 Packages</h2>
    401. 

  401. <span id="index-managing-packages"></span>
    402. 

  402. 

  403. <p>A package is a suite of programs usually distributed in binary form
    404. 

  404. which may also contain manual pages, documentation, or any other file
    405. 

  405. associated to a specific software.
    406. 

  406. </p>
    407. 

  407. <p>The package format used by qi is a simplified POSIX pax archive
    408. 

  408. compressed using lzip<a id="DOCF1" href="#FOOT1"><sup>1</sup></a>.  The
    409. 

  409. file extension for packages ends in &lsquo;<samp>.tlz</samp>&rsquo;.
    410. 

  410. </p>
    411. 

  411. <p>Both package installation and package de-installation are managed using
    412. 

  412. two important (internal) variables: &lsquo;<samp>${packagedir}</samp>&rsquo; and
    413. 

  413. &lsquo;<samp>${targetdir}</samp>&rsquo;, these values can be changed in the
    414. 

  414. configuration file or via options.
    415. 

  415. </p>
    416. 

  416. <p>&lsquo;<samp>${packagedir}</samp>&rsquo; is a common directory tree where the package
    417. 

  417. contents will be decompressed (will reside).
    418. 

  418. </p>
    419. 

  419. <p>&lsquo;<samp>${targetdir}</samp>&rsquo; is a target directory where the links will be
    420. 

  420. made by graft(1) taking &lsquo;<samp>${packagedir}/package_name</samp>&rsquo; into account.
    421. 

  421. </p>
    422. 

  422. <p>Packages are installed in self-contained directory trees and symbolic
    423. 

  423. links from a common area are made to the package files.  This allows
    424. 

  424. multiple versions of the same package to coexist on the same system.
    425. 

  425. </p>
    426. 

  426. <span id="Package-conflicts"></span><h3 class="section">4.1 Package conflicts</h3>
    427. 

  427. <span id="index-package-conflicts"></span>
    428. 

  428. 

  429. <p>All the links to install or remove a package are handled by graft(1).
    430. 

  430. Since multiple packages can be installed or removed at the same time,
    431. 

  431. certain conflicts may arise between the packages.
    432. 

  432. </p>
    433. 

  433. <p>graft<a id="DOCF2" href="#FOOT2"><sup>2</sup></a>
    434. 

  434. defines a CONFLICT as one of the following conditions:
    435. 

  435. </p>
    436. 

  436. <ul>
    437. 

  437. <li> If the package object is a directory and the target object exists but is
    438. 

  438. not a directory.
    439. 

  439. 

  440. </li><li> If the package object is not a directory and the target object exists
    441. 

  441. and is not a symbolic link.
    442. 

  442. 

  443. </li><li> If the package object is not a directory and the target object exists
    444. 

  444. and is a symbolic link to something other than the package object.
    445. 

  445. </li></ul>
    446. 

  446. 

  447. <p>The default behavior of qi for an incoming package is to ABORT if a
    448. 

  448. conflict arises.  When a package is going to be deleted, qi tells to
    449. 

  449. graft(1) to remove those parts that are not in conflict, leaving the
    450. 

  450. links to the belonging package.  This behavior can be forced if the
    451. 

  451. &ndash;prune option is given.
    452. 

  452. </p>
    453. 

  453. <span id="Installing-packages"></span><h3 class="section">4.2 Installing packages</h3>
    454. 

  454. <span id="index-package-installation"></span>
    455. 

  455. 

  456. <p>To install a single package, simply type:
    457. 

  457. </p>
    458. 

  458. <div class="example">
    459. 

  459. <pre class="example">qi install coreutils_8.30_i586-1@tools.tlz
    460. 

  460. </pre></div>
    461. 

  461. 

  462. <p>To install multiple packages at once, type:
    463. 

  463. </p>
    464. 

  464. <div class="example">
    465. 

  465. <pre class="example">qi install gcc_8.3.0_i586-1@devel.tlz rafaela_2.2_i586-1@legacy.tlz ...
    466. 

  466. </pre></div>
    467. 

  467. 

  468. <p>Warn about the files that will be linked:
    469. 

  469. </p>
    470. 

  470. <div class="example">
    471. 

  471. <pre class="example">qi warn bash_5.0_i586-1@shells.tlz
    472. 

  472. </pre></div>
    473. 

  473. 

  474. <p>This is to verify the content of a package before installing it.
    475. 

  475. </p>
    476. 

  476. <p>See the process of an installation:
    477. 

  477. </p>
    478. 

  478. <div class="example">
    479. 

  479. <pre class="example">qi install --verbose mariana_3.0_i586-1@woman.tlz
    480. 

  480. </pre></div>
    481. 

  481. 

  482. <p>A second &ndash;verbose or -v option gives more (very verbose).
    483. 

  483. </p>
    484. 

  484. <p>Installing package in a different location:
    485. 

  485. </p>
    486. 

  486. <div class="example">
    487. 

  487. <pre class="example">qi install --rootdir=/media/floppy lzip_1.21_i586-1@compressors.tlz
    488. 

  488. </pre></div>
    489. 

  489. 

  490. <p>Important: the &ndash;rootdir option assumes &lsquo;<samp>${targetdir}</samp>&rsquo; and
    491. 

  491. &lsquo;<samp>${packagedir}</samp>&rsquo;.  See the following example:
    492. 

  492. </p>
    493. 

  493. <div class="example">
    494. 

  494. <pre class="example">qi install --rootdir=/home/selk lzip_1.21_i586-1@compressors.tlz
    495. 

  495. </pre></div>
    496. 

  496. 

  497. <p>The content of &quot;lzip_1.21_i586-1@compressors.tlz&quot; will be decompressed
    498. 

  498. into &lsquo;<samp>/home/selk/pkgs/lzip_1.21_i586-1@compressors</samp>&rsquo;.
    499. 

  499. Assuming that the main binary for lzip is under
    500. 

  500. &lsquo;<samp>/home/selk/pkgs/lzip_1.21_i586-1@compressors/usr/bin/</samp>&rsquo;
    501. 

  501. the target for &quot;usr/bin&quot; will be created at &lsquo;<samp>/home/selk</samp>&rsquo;.  Considering
    502. 

  502. that you have exported the <code>PATH</code> as &lsquo;<samp>${HOME}/usr/bin</samp>&rsquo;, now the
    503. 

  503. system is able to see the recent lzip command.
    504. 

  504. </p>
    505. 

  505. <p>Installing from a list of packages using standard input:
    506. 

  506. </p>
    507. 

  507. <div class="example">
    508. 

  508. <pre class="example">qi install - &lt; PACKAGELIST.txt
    509. 

  509. </pre></div>
    510. 

  510. 

  511. <p>Or in combination with another tool:
    512. 

  512. </p><div class="example">
    513. 

  513. <pre class="example">sort -u PACKAGELIST.txt | qi install -
    514. 

  514. </pre></div>
    515. 

  515. 

  516. <p>The sort command will read and sorts the list of declared packages,
    517. 

  517. while trying to have unique entries for each statement.  The output
    518. 

  518. produced is captured by Qi to install each package.
    519. 

  519. </p>
    520. 

  520. <p>An example of a list containing package names is:
    521. 

  521. </p><div class="example">
    522. 

  522. <pre class="example">/var/cache/qi/packages/amd64/tcl_8.6.9_amd64-1@devel.tlz
    523. 

  523. /var/cache/qi/packages/amd64/tk_8.6.9.1_amd64-1@devel.tlz
    524. 

  524. /var/cache/qi/packages/amd64/vala_0.42.3_amd64-1@devel.tlz
    525. 

  525. </pre></div>
    526. 

  526. 

  527. <span id="Removing-packages"></span><h3 class="section">4.3 Removing packages</h3>
    528. 

  528. <span id="index-package-de_002dinstallation"></span>
    529. 

  529. 

  530. <p>To remove a package, simply type:
    531. 

  531. </p>
    532. 

  532. <div class="example">
    533. 

  533. <pre class="example">qi remove xz_5.2.4_i586-1@compressors.tlz
    534. 

  534. </pre></div>
    535. 

  535. 

  536. <p>Remove command will match the package name using &lsquo;<samp>${packagedir}</samp>&rsquo; as
    537. 

  537. prefix.  For example, if the value of &lsquo;<samp>${packagedir}</samp>&rsquo; has been
    538. 

  538. set to /usr/pkg, this will be equal to:
    539. 

  539. </p>
    540. 

  540. <div class="example">
    541. 

  541. <pre class="example">qi remove /usr/pkg/xz_5.2.4_i586-1@compressors
    542. 

  542. </pre></div>
    543. 

  543. 

  544. <p>Detailed output:
    545. 

  545. </p>
    546. 

  546. <div class="example">
    547. 

  547. <pre class="example">qi remove --verbose /usr/pkg/xz_5.2.4_i586-1@compressors
    548. 

  548. </pre></div>
    549. 

  549. 

  550. <p>A second &ndash;verbose or -v option gives more (very verbose).
    551. 

  551. </p>
    552. 

  552. <p>By default the remove command does not preserve a package directory after
    553. 

  553. removing its links from &lsquo;<samp>${targetdir}</samp>&rsquo;, but this behavior can be
    554. 

  554. changed if the &ndash;keep option is passed:
    555. 

  555. </p>
    556. 

  556. <div class="example">
    557. 

  557. <pre class="example">qi remove --keep /usr/pkg/lzip_1.21_i586-1@compressors
    558. 

  558. </pre></div>
    559. 

  559. 

  560. <p>This means that the links to the package can be reactivated, later:
    561. 

  561. </p>
    562. 

  562. <div class="example">
    563. 

  563. <pre class="example">cd /usr/pkg &amp;&amp; graft -i lzip_1.21_i586-1@compressors
    564. 

  564. </pre></div>
    565. 

  565. 

  566. <p>Removing package from a different location:
    567. 

  567. </p>
    568. 

  568. <div class="example">
    569. 

  569. <pre class="example">qi remove --rootdir=/home/cthulhu xz_5.2.4_i586-1@compressors
    570. 

  570. </pre></div>
    571. 

  571. 

  572. <p>Removing a package using standard input:
    573. 

  573. </p>
    574. 

  574. <div class="example">
    575. 

  575. <pre class="example">echo vala_0.42.3_amd64-1@devel | qi remove -
    576. 

  576. </pre></div>
    577. 

  577. 

  578. <p>This will match with the package directory.
    579. 

  579. </p>
    580. 

  580. <span id="Upgrading-packages"></span><h3 class="section">4.4 Upgrading packages</h3>
    581. 

  581. <span id="index-package-upgrade"></span>
    582. 

  582. 

  583. <p>The upgrade command inherits the properties of the installation and removal
    584. 

  584. process.  To make sure that a package is updated, the package is installed
    585. 

  585. in a temporary directory taking &lsquo;<samp>${packagedir}</samp>&rsquo; into account.  Once
    586. 

  586. the incoming package is pre-installed, qi can proceed to search and delete
    587. 

  587. packages that have the same name (considered as previous ones).  Finally,
    588. 

  588. the package is re-installed at its final location and the temporary
    589. 

  589. directory is removed.
    590. 

  590. </p>
    591. 

  591. <p>Since updating a package can be crucial and so to perform a successful
    592. 

  592. upgrade, from start to finish, you will want to ignore some important
    593. 

  593. system signals during the upgrade process, those signals are SIGHUP,
    594. 

  594. SIGINT, SIGQUIT, SIGABRT, and SIGTERM.
    595. 

  595. </p>
    596. 

  596. <p>To upgrade a package, just type:
    597. 

  597. </p>
    598. 

  598. <div class="example">
    599. 

  599. <pre class="example">qi upgrade gcc_9.0.1_i586-1@devel.tlz
    600. 

  600. </pre></div>
    601. 

  601. 

  602. <p>This will proceed to upgrade &quot;gcc_9.0.1_i586-1@devel&quot; removing any other
    603. 

  603. version of &quot;gcc&quot; (if any).
    604. 

  604. </p>
    605. 

  605. <p>If you want to keep the package directories of versions found during the
    606. 

  606. upgrade process, just pass:
    607. 

  607. </p>
    608. 

  608. <div class="example">
    609. 

  609. <pre class="example">qi upgrade --keep gcc_9.0.1_i586-1@devel.tlz
    610. 

  610. </pre></div>
    611. 

  611. 

  612. <p>To see the upgrade process:
    613. 

  613. </p>
    614. 

  614. <div class="example">
    615. 

  615. <pre class="example">qi upgrade --verbose gcc_9.0.1_i586-1@devel.tlz
    616. 

  616. </pre></div>
    617. 

  617. 

  618. <p>A second &ndash;verbose or -v option gives more (very verbose).
    619. 

  619. </p>
    620. 

  620. <p>To force the upgrade of an existing package:
    621. 

  621. </p>
    622. 

  622. <div class="example">
    623. 

  623. <pre class="example">qi upgrade --force gcc_9.0.1_i586-1@devel.tlz
    624. 

  624. </pre></div>
    625. 

  625. 

  626. <span id="Package-blacklist"></span><h4 class="subsection">4.4.1 Package blacklist</h4>
    627. 

  627. <span id="index-package-blacklist"></span>
    628. 

  628. 

  629. <p>To implement general package facilities, either to install, remove or
    630. 

  630. maintain the hierarchy of packages in a clean manner, qi makes use of the
    631. 

  631. pruning operation via graft(1) by default:
    632. 

  632. </p>
    633. 

  633. <p>There is a risk if those are crucial packages for the proper functioning
    634. 

  634. of the system, because it implies the deactivation of symbolic from the
    635. 

  635. target directory, <em>especially</em> when transitioning an incoming package
    636. 

  636. into its final location during an upgrade.
    637. 

  637. </p>
    638. 

  638. <p>A blacklist of package names has been devised for the case where
    639. 

  639. a user decides to upgrade all the packages in the system, or
    640. 

  640. just the crucial ones, such as the C library.
    641. 

  641. </p>
    642. 

  642. <p>The blacklist is related to the upgrade command only, consists in installing
    643. 

  643. a package instead of updating it or removing previous versions of it;
    644. 

  644. the content of the package will be updated over the existing content at
    645. 

  645. &lsquo;<samp>${packagedir}</samp>&rsquo;, while the existing links from
    646. 

  646. &lsquo;<samp>${targetdir}</samp>&rsquo; will be preserved.  A pruning of links will be
    647. 

  647. carried out in order to re-link possible differences with the recent
    648. 

  648. content, this helps to avoid leaving dead links in the target directory.
    649. 

  649. </p>
    650. 

  650. <p>Package names for the blacklist to be declared must be set from the
    651. 

  651. configuration file.  By default, it is declared using the package name,
    652. 

  652. which is more than enough for critical system packages, but if you want to
    653. 

  653. be more specific, you can declare a package using:
    654. 

  654. &lsquo;<samp>${pkgname}_${pkgversion}_${arch}-${release}</samp>&rsquo; where
    655. 

  655. the package category is avoided for common matching.  See
    656. 

  656. <a href="#Recipes">Special variables</a> for a description of these variables.
    657. 

  657. </p>
    658. 

  658. <hr>
    659. 

  659. <span id="Recipes"></span><div class="header">
    660. 

  660. <p>
    661. 

  661. Next: <a href="#Order-files" accesskey="n" rel="next">Order files</a>, Previous: <a href="#Packages" accesskey="p" rel="prev">Packages</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Index" title="Index" rel="index">Index</a>]</p>
    662. 

  662. </div>
    663. 

  663. <span id="Recipes-1"></span><h2 class="chapter">5 Recipes</h2>
    664. 

  664. <span id="index-recipes"></span>
    665. 

  665. 

  666. <p>A recipe is a file telling qi what to do.  Most often, the recipe tells
    667. 

  667. qi how to build a binary package from a source tarball.
    668. 

  668. </p>
    669. 

  669. <p>A recipe has two parts: a list of variable definitions and a list of
    670. 

  670. sections.  By convention, the syntax of a section is:
    671. 

  671. </p>
    672. 

  672. <div class="example">
    673. 

  673. <pre class="example">section_name()
    674. 

  674. {
    675. 

  675.     section lines
    676. 

  676. }
    677. 

  677. </pre></div>
    678. 

  678. 

  679. <p>The section name is followed by parentheses, one newline and an opening
    680. 

  680. brace.  The line finishing the section contains just a closing brace.
    681. 

  681. The section names or the function names currently recognized are
    682. 

  682. &lsquo;<samp>build</samp>&rsquo;.
    683. 

  683. </p>
    684. 

  684. <p>The &lsquo;<samp>build</samp>&rsquo; section (or <strong>shell function</strong>) is an augmented
    685. 

  685. shell script that contains the main instructions to build software
    686. 

  686. from source.
    687. 

  687. </p>
    688. 

  688. <p>If there are other functions defined by the packager, Qi detects them
    689. 

  689. for later execution.
    690. 

  690. </p>
    691. 

  691. <span id="Variables"></span><h3 class="section">5.1 Variables</h3>
    692. 

  692. <span id="index-variables"></span>
    693. 

  693. 

  694. <p>A &quot;variable&quot; is a <strong>shell variable</strong> defined either in <samp>qirc</samp>
    695. 

  695. or in a recipe to represent a string of text, called the variable&rsquo;s
    696. 

  696. &quot;value&quot;.  These values are substituted by explicit request in the
    697. 

  697. definitions of other variables or in calls to external commands.
    698. 

  698. </p>
    699. 

  699. <p>Variables can represent lists of file names, options to pass to
    700. 

  700. compilers, programs to run, directories to look in for source files,
    701. 

  701. directories to write output to, or anything else you can imagine.
    702. 

  702. </p>
    703. 

  703. <p>Definitions of variables in qi have four levels of precedence.
    704. 

  704. Options which define variables from the command-line override those
    705. 

  705. specified in the <samp>qirc</samp> file, while variables defined in the recipe
    706. 

  706. override those specified in <samp>qirc</samp>, taking priority over those
    707. 

  707. variables set by command-line options.  Finally, the variables have
    708. 

  708. default values if they are not defined anywhere.
    709. 

  709. </p>
    710. 

  710. <p>Options that set variables through the command-line can only reference
    711. 

  711. variables defined in <samp>qirc</samp> and variables with default values.
    712. 

  712. </p>
    713. 

  713. <p>Definitions of variables in <samp>qirc</samp> can only reference variables
    714. 

  714. previously defined in <samp>qirc</samp> and variables with default values.
    715. 

  715. </p>
    716. 

  716. <p>Definitions of variables in the recipe can only reference variables
    717. 

  717. set by the command-line, variables previously defined in the recipe,
    718. 

  718. variables defined in <samp>qirc</samp>, and variables with default values.
    719. 

  719. </p>
    720. 

  720. <span id="Special-variables"></span><h3 class="section">5.2 Special variables</h3>
    721. 

  721. <span id="index-special-variables"></span>
    722. 

  722. 

  723. <p>There are variables which can only be set using the command line options or
    724. 

  724. via <samp>qirc</samp>, there are other special variables which can be defined or
    725. 

  725. redefined in a recipe.  See the following definitions:
    726. 

  726. </p>
    727. 

  727. <p>&lsquo;<samp>outdir</samp>&rsquo; is the directory where the packages produced are written.
    728. 

  728. This variable can be redefined per-recipe.  Default sets to
    729. 

  729. &lsquo;<samp>/var/cache/qi/packages</samp>&rsquo;.
    730. 

  730. </p>
    731. 

  731. <p>&lsquo;<samp>worktree</samp>&rsquo; is the working tree where archives, patches, and recipes
    732. 

  732. are expected.  This variable can not be redefined in the recipe.  Default
    733. 

  733. sets to &lsquo;<samp>/usr/src/qi</samp>&rsquo;.
    734. 

  734. </p>
    735. 

  735. <p>&lsquo;<samp>tardir</samp>&rsquo; is defined in the recipe to the directory where the tarball
    736. 

  736. containing the source can be found.  The full name of the tarball is
    737. 

  737. composed as &lsquo;<samp>${tardir}/$tarname</samp>&rsquo;.  Its value is available in the
    738. 

  738. recipe as &lsquo;<samp>${tardir}</samp>&rsquo;; a value of . for &lsquo;<samp>tardir</samp>&rsquo; sets it to
    739. 

  739. the value of CWD (Current Working Directory), this is where the recipe
    740. 

  740. lives.
    741. 

  741. </p>
    742. 

  742. <p>&lsquo;<samp>arch</samp>&rsquo; is the architecture to compose the package name.  Its value is
    743. 

  743. available in the recipe as &lsquo;<samp>${arch}</samp>&rsquo;.  Default value is the one
    744. 

  744. that was set in the Qi configuration.
    745. 

  745. </p>
    746. 

  746. <p>&lsquo;<samp>jobs</samp>&rsquo; is the number of parallel jobs to pass to the compiler.  Its
    747. 

  747. value is available in the recipe as &lsquo;<samp>${jobs}</samp>&rsquo;.  The default value
    748. 

  748. is 1.
    749. 

  749. </p>
    750. 

  750. <p>The two variables &lsquo;<samp>${srcdir}</samp>&rsquo; and &lsquo;<samp>${destdir}</samp>&rsquo; can be
    751. 

  751. set in the recipe, as any other variable, but if they are not, qi uses
    752. 

  752. default values for them when building a package.
    753. 

  753. </p>
    754. 

  754. <p>&lsquo;<samp>srcdir</samp>&rsquo; contains the source code to be compiled, and defaults to
    755. 

  755. &lsquo;<samp>${program}-${version}</samp>&rsquo;.  &lsquo;<samp>destdir</samp>&rsquo; is the place where the
    756. 

  756. built package will be installed, and defaults to
    757. 

  757. &lsquo;<samp>${TMPDIR}/package-${program}</samp>&rsquo;.
    758. 

  758. </p>
    759. 

  759. <p>If &lsquo;<samp>pkgname</samp>&rsquo; is left undefined, the special variable &lsquo;<samp>program</samp>&rsquo;
    760. 

  760. is assigned by default.  If &lsquo;<samp>pkgversion</samp>&rsquo; is left undefined, the
    761. 

  761. special variable &lsquo;<samp>version</samp>&rsquo; is assigned by default.
    762. 

  762. </p>
    763. 

  763. <p>&lsquo;<samp>pkgname</samp>&rsquo; and &lsquo;<samp>pkgversion</samp>&rsquo; along with: &lsquo;<samp>version</samp>&rsquo;, &lsquo;<samp>arch</samp>&rsquo;,
    764. 

  764. &lsquo;<samp>release</samp>&rsquo;, and (optionally) &lsquo;<samp>pkgcategory</samp>&rsquo; are used to produce the
    765. 

  765. package name in the form:
    766. 

  766. &lsquo;<samp>${pkgname}_${pkgversion}_${arch}-${release}[@${pkgcategory}].tlz</samp>&rsquo;
    767. 

  767. </p>
    768. 

  768. <p>&lsquo;<samp>pkgcategory</samp>&rsquo; is an optional special variable that can be defined on the
    769. 

  769. recipe to categorize the package name.  If it is defined, then the
    770. 

  770. package output will be composed as
    771. 

  771. &lsquo;<samp>${pkgname}_${pkgversion}_${arch}-${release}[@${pkgcategory}.tlz</samp>&rsquo;.
    772. 

  772. Automatically, the value of &lsquo;<samp>pkgcategory</samp>&rsquo; will be prefixed using the
    773. 

  773. &lsquo;<samp>@</samp>&rsquo; (at) symbol which will be added to the last part of the package name.
    774. 

  774. </p>
    775. 

  775. <p>A special variable called &lsquo;<samp>replace</samp>&rsquo; can be used to declare package names
    776. 

  776. that will be replaced at installation time.
    777. 

  777. </p>
    778. 

  778. <p>The special variables &lsquo;<samp>keep_srcdir</samp>&rsquo; and &lsquo;<samp>keep_destdir</samp>&rsquo; are provided
    779. 

  779. in order to preserve the directories &lsquo;<samp>${srcdir}</samp>&rsquo; or &lsquo;<samp>${destdir}</samp>&rsquo;,
    780. 

  780. if those exists as such.  Note: The declaration of these variables are subject
    781. 

  781. to manual deactivation; its purpose in recipes is to preserve the directories
    782. 

  782. that relate to the package&rsquo;s build (source) and destination directory, that is
    783. 

  783. so that another recipe can get a new package (or meta package) from there.  For
    784. 

  784. example, the declarations can be done as:
    785. 

  785. </p>
    786. 

  786. <div class="example">
    787. 

  787. <pre class="example">keep_srcdir=keep_srcdir
    788. 

  788. keep_destdir=keep_destdir
    789. 

  789. </pre></div>
    790. 

  790. 

  791. <p>Then from another recipe you would proceed to copy the necessary files that
    792. 

  792. will compose the meta package, from the main function you must deactivate
    793. 

  793. the variables at the end:
    794. 

  794. </p>
    795. 

  795. <div class="example">
    796. 

  796. <pre class="example">unset -v keep_srcdir keep_destdir
    797. 

  797. </pre></div>
    798. 

  798. 

  799. <p>This will leave the &rsquo;keep_srcdir&rsquo; and &rsquo;keep_destdir&rsquo; variables blank to
    800. 

  800. continue with the rest of the recipes.
    801. 

  801. </p>
    802. 

  802. <p>The special variable &lsquo;<samp>opt_skiprecipe</samp>&rsquo; is available when you need to
    803. 

  803. ignore a recipe cleanly, continuing with the next recipe.  May you add a
    804. 

  804. conditional test then set it as &lsquo;<samp>opt_skiprecipe=opt_skiprecipe</samp>&rsquo;.
    805. 

  805. </p>
    806. 

  806. <p>The variable &lsquo;<samp>tarlz_compression_options</samp>&rsquo; can be used to change the
    807. 

  807. default compression options in tarlz(1), default sets to &lsquo;<samp>-9 --solid</samp>&rsquo;.
    808. 

  808. For example if the variable is declared as:
    809. 

  809. </p>
    810. 

  810. <div class="example">
    811. 

  811. <pre class="example">tarlz_compression_options=&quot;-0 --bsolid&quot;
    812. 

  812. </pre></div>
    813. 

  813. 

  814. <p>It will change the granularity of tarlz(1) by using the &lsquo;<samp>--bsolid</samp>&rsquo;
    815. 

  815. option <a id="DOCF3" href="#FOOT3"><sup>3</sup></a>,
    816. 

  816. as well as increasing the compression speed by lowering the compression
    817. 

  817. level with &lsquo;<samp>-0</samp>&rsquo;.
    818. 

  818. </p>
    819. 

  819. <p>This is only recommended for recipes where testing, or faster processing is
    820. 

  820. desired to create the packaged file more quickly.  It is not recommended for
    821. 

  821. production or general distribution of binary packages.
    822. 

  822. </p>
    823. 

  823. <p>A typical recipe contains the following variables:
    824. 

  824. </p>
    825. 

  825. <ul>
    826. 

  826. <li> &lsquo;<samp>program</samp>&rsquo;: Software name.
    827. 

  827. 

  828. <p>It matches the source name.  It is also used to compose the name of the
    829. 

  829. package if &lsquo;<samp>${pkgname}</samp>&rsquo; is not specified.
    830. 

  830. </p>
    831. 

  831. </li><li> &lsquo;<samp>version</samp>&rsquo;: Software version.
    832. 

  832. 

  833. <p>It matches the source name.  It is also used to compose the version of the
    834. 

  834. package if &lsquo;<samp>${pkgversion}</samp>&rsquo; is not specified.
    835. 

  835. </p>
    836. 

  836. </li><li> &lsquo;<samp>arch</samp>&rsquo;: Software architecture.
    837. 

  837. 

  838. <p>It is used to compose the architecture of the package in which it is
    839. 

  839. build.
    840. 

  840. </p>
    841. 

  841. </li><li> &lsquo;<samp>release</samp>&rsquo;: Release number.
    842. 

  842. 

  843. <p>This is used to reflect the release number of the package.  It is
    844. 

  844. recommended to increase this number after any significant change in
    845. 

  845. the recipe or post-install script.
    846. 

  846. </p>
    847. 

  847. </li><li> &lsquo;<samp>pkgcategory</samp>&rsquo;: Package category.
    848. 

  848. 

  849. <p>Optional but recommended variable to categorize the package name when it is
    850. 

  850. created.
    851. 

  851. </p></li></ul>
    852. 

  852. 

  853. <p>Obtaining sources over the network must be declared in the recipe using
    854. 

  854. the &lsquo;<samp>fetch</samp>&rsquo; variable.
    855. 

  855. </p>
    856. 

  856. <p>The variables &lsquo;<samp>netget</samp>&rsquo; and &lsquo;<samp>rsync</samp>&rsquo; can be defined in <samp>qirc</samp>
    857. 

  857. to establish a network downloader in order to get the sources.  If they
    858. 

  858. are not defined, qi uses default values:
    859. 

  859. </p>
    860. 

  860. <p>&lsquo;<samp>netget</samp>&rsquo; is the general network downloader tool, defaults sets to
    861. 

  861. &lsquo;<samp>wget2 -c -w1 -t3 --no-check-certificate</samp>&rsquo;.
    862. 

  862. </p>
    863. 

  863. <p>&lsquo;<samp>rsync</samp>&rsquo; is the network tool for sources containing the prefix for
    864. 

  864. the RSYNC protocol, default sets to
    865. 

  865. &lsquo;<samp>rsync -v -a -L -z -i --progress</samp>&rsquo;.
    866. 

  866. </p>
    867. 

  867. <p>The variable &lsquo;<samp>description</samp>&rsquo; is used to print the package description
    868. 

  868. when a package is installed.
    869. 

  869. </p>
    870. 

  870. <p>A description has two parts: a brief description, and a long description.
    871. 

  871. By convention, the syntax of &lsquo;<samp>description</samp>&rsquo; is:
    872. 

  872. </p>
    873. 

  873. <div class="example">
    874. 

  874. <pre class="example">description=&quot;
    875. 

  875. Brief description.
    876. 

  876. 

  877. Long description.
    878. 

  878. &quot;
    879. 

  879. </pre></div>
    880. 

  880. 

  881. <p>The first line of the value represented is a brief description of the
    882. 

  882. software (called &quot;blurb&quot;).  A blank line separates the <em>brief
    883. 

  883. description</em> from the <em>long description</em>, which should contain a more
    884. 

  884. descriptive description of the software.
    885. 

  885. </p>
    886. 

  886. <p>An example looks like:
    887. 

  887. </p>
    888. 

  888. <div class="example">
    889. 

  889. <pre class="example">description=&quot;
    890. 

  890. The GNU core utilities.
    891. 

  891. 

  892. The GNU core utilities are the basic file, shell and text manipulation
    893. 

  893. utilities of the GNU operating system.  These are the core utilities
    894. 

  894. which are expected to exist on every operating system.
    895. 

  895. &quot;
    896. 

  896. </pre></div>
    897. 

  897. 

  898. <p>Please consider a length limit of 78 characters as maximum, because the same
    899. 

  899. one would be used on the meta file creation.  See
    900. 

  900. <a href="#Recipes">The meta file</a> section.
    901. 

  901. </p>
    902. 

  902. <p>The &lsquo;<samp>homepage</samp>&rsquo; variable is used to declare the main site or home page:
    903. 

  903. </p>
    904. 

  904. <div class="example">
    905. 

  905. <pre class="example">homepage=https://www.gnu.org/software/gcc
    906. 

  906. </pre></div>
    907. 

  907. 

  908. <p>The variable &lsquo;<samp>license</samp>&rsquo; is used for license information<a id="DOCF4" href="#FOOT4"><sup>4</sup></a>.
    909. 

  909. Some code in the program can be covered by license A, license B, or
    910. 

  910. license C.  For &quot;separate licensing&quot; or &quot;heterogeneous licensing&quot;, we
    911. 

  911. suggest using <strong>|</strong> for a disjunction, <strong>&amp;</strong> for a conjunction
    912. 

  912. (if that ever happens in a significant way), and comma for heterogeneous
    913. 

  913. licensing.  Comma would have lower precedence, plus added special terms.
    914. 

  914. </p>
    915. 

  915. <div class="example">
    916. 

  916. <pre class="example">license=&quot;LGPL, GPL | Artistic - added permission&quot;
    917. 

  917. </pre></div>
    918. 

  918. 

  919. <span id="Writing-recipes"></span><h3 class="section">5.3 Writing recipes</h3>
    920. 

  920. <span id="index-writing-recipes"></span>
    921. 

  921. 

  922. <p>Originally, Qi was designed for the series of Dragora GNU/Linux-Libre 3;
    923. 

  923. this doesn&rsquo;t mean you can&rsquo;t use it in another distribution, just that if
    924. 

  924. you do, you&rsquo;ll have to try it out for yourself. To help with this, here
    925. 

  925. are some references to well-written recipes:
    926. 

  926. </p>
    927. 

  927. <ul>
    928. 

  928. <li> <a href="https://git.savannah.nongnu.org/cgit/dragora.git/tree/recipes">https://git.savannah.nongnu.org/cgit/dragora.git/tree/recipes</a>
    929. 

  929. </li><li> <a href="https://notabug.org/dragora/dragora/src/master/recipes">https://notabug.org/dragora/dragora/src/master/recipes</a>
    930. 

  930. </li><li> <a href="https://notabug.org/dragora/dragora-extras/src/master/recipes">https://notabug.org/dragora/dragora-extras/src/master/recipes</a>
    931. 

  931. </li><li> <a href="https://git.savannah.nongnu.org/cgit/dragora/dragora-extras.git/tree/recipes">https://git.savannah.nongnu.org/cgit/dragora/dragora-extras.git/tree/recipes</a>
    932. 

  932. </li></ul>
    933. 

  933. 

  934. <span id="Building-packages"></span><h3 class="section">5.4 Building packages</h3>
    935. 

  935. <span id="index-package-build"></span>
    936. 

  936. 

  937. <p>A recipe is any valid regular file.  Qi sets priorities for reading a
    938. 

  938. recipe, the order in which qi looks for a recipe is:
    939. 

  939. </p>
    940. 

  940. <ol>
    941. 

  941. <li> Current working directory.
    942. 

  942. 

  943. </li><li> If the specified path name does not contain &quot;recipe&quot; as the last
    944. 

  944. component.  Qi will complete it by adding &quot;recipe&quot; to the path name.
    945. 

  945. 

  946. </li><li> If the recipe is not in the current working directory, it will be
    947. 

  947. searched under &lsquo;<samp>${worktree}/recipes</samp>&rsquo;.  The last component will be
    948. 

  948. completed adding &quot;recipe&quot; to the specified path name.
    949. 

  949. </li></ol>
    950. 

  950. 

  951. <p>To build a single package, type:
    952. 

  952. </p>
    953. 

  953. <div class="example">
    954. 

  954. <pre class="example">qi build x-apps/xterm
    955. 

  955. </pre></div>
    956. 

  956. 

  957. <p>Multiple jobs can be passed to the compiler to speed up the build process:
    958. 

  958. </p>
    959. 

  959. <div class="example">
    960. 

  960. <pre class="example">qi build --jobs 3 x-apps/xterm
    961. 

  961. </pre></div>
    962. 

  962. 

  963. <p>Update or install the produced package (if not already installed) when the
    964. 

  964. build command ends:
    965. 

  965. </p>
    966. 

  966. <div class="example">
    967. 

  967. <pre class="example">qi build -j3 --upgrade x-apps/xterm
    968. 

  968. </pre></div>
    969. 

  969. 

  970. <p>Only process a recipe but do not create the binary package:
    971. 

  971. </p>
    972. 

  972. <div class="example">
    973. 

  973. <pre class="example">qi build --no-package dict/aspell
    974. 

  974. </pre></div>
    975. 

  975. 

  976. <p>The options &ndash;install or &ndash;upgrade have no effect when &ndash;no-package
    977. 

  977. is given.
    978. 

  978. </p>
    979. 

  979. <p>This is useful to inspect the build process of the above recipe:
    980. 

  980. </p>
    981. 

  981. <p>qi build &ndash;keep &ndash;no-package dict/aspell 2&gt;&amp;1 | tee aspell-log.txt
    982. 

  982. </p>
    983. 

  983. <p>The &ndash;keep option could preserve the source directory and the destination
    984. 

  984. directory for later inspection.  A log file of the build process will be
    985. 

  985. created redirecting both, standard error and standard output to tee(1).
    986. 

  986. </p>
    987. 

  987. <span id="Variables-from-the-environment"></span><h3 class="section">5.5 Variables from the environment</h3>
    988. 

  988. <span id="index-environment-variables"></span>
    989. 

  989. 

  990. <p>Qi has environment variables which can be used at build time:
    991. 

  991. </p>
    992. 

  992. <p>The variable <code>TMPDIR</code> sets the temporary directory for sources, which is
    993. 

  993. used for package extractions (see <a href="#Examining-packages">Examining packages</a>) and is
    994. 

  994. prepended to the value of &lsquo;<samp>${srcdir}</samp>&rsquo; and &lsquo;<samp>${destdir}</samp>&rsquo; in
    995. 

  995. build command.  By convention its default value is equal to
    996. 

  996. &lsquo;<samp>/usr/src/qi/build</samp>&rsquo;.
    997. 

  997. </p>
    998. 

  998. <p>The variables <code>QICFLAGS</code>, <code>QICXXFLAGS</code>, <code>QILDFLAGS</code>, and
    999. 

  999. <code>QICPPFLAGS</code> have no effect by default.  The environment variables
    1000. 

  1000. such as <code>CFLAGS</code>, <code>CXXFLAGS</code>, <code>LDFLAGS</code>, and <code>CPPFLAGS</code>
    1001. 

  1001. are unset at compile time:
    1002. 

  1002. </p>
    1003. 

  1003. <p>Recommended practice is to set variables in the command line of
    1004. 

  1004. &lsquo;<samp>configure</samp>&rsquo; or <em>make(1)</em> instead of exporting to the
    1005. 

  1005. environment.  As follows:
    1006. 

  1006. </p>
    1007. 

  1007. <p><a href="https://www.gnu.org/software/make/manual/html_node/Environment.html">https://www.gnu.org/software/make/manual/html_node/Environment.html</a>
    1008. 

  1008. </p><blockquote>
    1009. 

  1009. <p>It is not wise for makefiles to depend for their functioning on environment
    1010. 

  1010. variables set up outside their control, since this would cause different
    1011. 

  1011. users to get different results from the same makefile.  This is against the
    1012. 

  1012. whole purpose of most makefiles.
    1013. 

  1013. </p></blockquote>
    1014. 

  1014. 

  1015. <p>Setting environment variables for configure is deprecated because running
    1016. 

  1016. configure in varying environments can be dangerous.
    1017. 

  1017. </p>
    1018. 

  1018. <p><a href="https://gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.69/html_node/Defining-Variables.html">https://gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.69/html_node/Defining-Variables.html</a>
    1019. 

  1019. </p><blockquote>
    1020. 

  1020. <p>Variables not defined in a site shell script can be set in the environment
    1021. 

  1021. passed to configure.  However, some packages may run configure again
    1022. 

  1022. during the build, and the customized values of these variables may be
    1023. 

  1023. lost.  In order to avoid this problem, you should set them in the
    1024. 

  1024. configure command line, using &lsquo;<samp>VAR=value</samp>&rsquo;.  For example:
    1025. 

  1025. </p>
    1026. 

  1026. <p><code>./configure CC=/usr/local2/bin/gcc</code>
    1027. 

  1027. </p></blockquote>
    1028. 

  1028. 

  1029. <p><a href="https://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.69/html_node/Setting-Output-Variables.html">https://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.69/html_node/Setting-Output-Variables.html</a>
    1030. 

  1030. </p><blockquote>
    1031. 

  1031. <p>If for instance the user runs &lsquo;<samp>CC=bizarre-cc ./configure</samp>&rsquo;, then the cache,
    1032. 

  1032. config.h, and many other output files depend upon bizarre-cc being the C
    1033. 

  1033. compiler.  If for some reason the user runs ./configure again, or if it is
    1034. 

  1034. run via &lsquo;<samp>./config.status --recheck</samp>&rsquo;, (See Automatic Remaking, and see
    1035. 

  1035. config.status Invocation), then the configuration can be inconsistent,
    1036. 

  1036. composed of results depending upon two different compilers.
    1037. 

  1037. [...]
    1038. 

  1038. Indeed, while configure can notice the definition of CC in &lsquo;<samp>./configure
    1039. 

  1039. CC=bizarre-cc</samp>&rsquo;, it is impossible to notice it in &lsquo;<samp>CC=bizarre-cc
    1040. 

  1040. ./configure</samp>&rsquo;, which, unfortunately, is what most users do.
    1041. 

  1041. [...]
    1042. 

  1042. configure: error: changes in the environment can compromise the build.
    1043. 

  1043. </p></blockquote>
    1044. 

  1044. 

  1045. <p>If the <code>SOURCE_DATE_EPOCH</code> environment variable is set to a UNIX timestamp
    1046. 

  1046. (defined as the number of seconds, excluding leap seconds, since 01 Jan 1970
    1047. 

  1047. 00:00:00 UTC.); then the given timestamp will be used to overwrite any newer
    1048. 

  1048. timestamps on the package contents (when it is created).  More information
    1049. 

  1049. about this can be found at
    1050. 

  1050. <a href="https://reproducible-builds.org/specs/source-date-epoch/">https://reproducible-builds.org/specs/source-date-epoch/</a>.
    1051. 

  1051. </p>
    1052. 

  1052. <span id="The-meta-file"></span><h3 class="section">5.6 The meta file</h3>
    1053. 

  1053. <span id="index-the-meta-file"></span>
    1054. 

  1054. 

  1055. <p>The &quot;meta file&quot; is a regular file created during the build process, it
    1056. 

  1056. contains information about the package such as package name, package
    1057. 

  1057. version, architecture, release, fetch address, description, and other
    1058. 

  1058. minor data extracted from processed recipes.  The name of the file is
    1059. 

  1059. generated as &lsquo;<samp>${full_pkgname}.tlz.txt</samp>&rsquo;, and its purpose is to
    1060. 

  1060. reflect essential information to the user without having to look inside
    1061. 

  1061. the package content.  The file format is also intended to be used by
    1062. 

  1062. other scripts or by common Unix tools.
    1063. 

  1063. </p>
    1064. 

  1064. <p>The content of a meta file looks like:
    1065. 

  1065. </p>
    1066. 

  1066. <div class="example">
    1067. 

  1067. <pre class="example">#
    1068. 

  1068. # Pattern scanning and processing language.
    1069. 

  1069. #
    1070. 

  1070. # The awk utility interprets a special-purpose programming language
    1071. 

  1071. # that makes it possible to handle simple data-reformatting jobs
    1072. 

  1072. # with just a few lines of code.  It is a free version of 'awk'.
    1073. 

  1073. #
    1074. 

  1074. # GNU awk implements the AWK utility which is part of
    1075. 

  1075. # IEEE Std 1003.1 Shell and Utilities (XCU).
    1076. 

  1076. #
    1077. 

  1077. 

  1078. QICFLAGS=&quot;-O2&quot;
    1079. 

  1079. QICXXFLAGS=&quot;-O2&quot;
    1080. 

  1080. QILDFLAGS=&quot;&quot;
    1081. 

  1081. QICPPFLAGS=&quot;&quot;
    1082. 

  1082. pkgname=gawk
    1083. 

  1083. pkgversion=5.0.1
    1084. 

  1084. arch=amd64
    1085. 

  1085. release=1
    1086. 

  1086. pkgcategory=&quot;tools&quot;
    1087. 

  1087. full_pkgname=gawk_5.0.1_amd64-1@tools
    1088. 

  1088. blurb=&quot;Pattern scanning and processing language.&quot;
    1089. 

  1089. homepage=&quot;https://www.gnu.org/software/gawk&quot;
    1090. 

  1090. license=&quot;GPLv3+&quot;
    1091. 

  1091. fetch=&quot;https://ftp.gnu.org/gnu/gawk/gawk-5.0.1.tar.lz&quot;
    1092. 

  1092. replace=&quot;&quot;
    1093. 

  1093. </pre></div>
    1094. 

  1094. 

  1095. <p>A package descriptions is extracted from the variable &lsquo;<samp>description</samp>&rsquo;
    1096. 

  1096. where each line is interpreted literally and pre-formatted to fit in
    1097. 

  1097. (exactly) <strong>80 columns</strong>, plus the character &lsquo;<samp>#</samp>&rsquo; and a blank
    1098. 

  1098. space is prefixed to every line (shell comments).
    1099. 

  1099. </p>
    1100. 

  1100. <p>In addition to the Special variables, there are implicit variables such as
    1101. 

  1101. &lsquo;<samp>blurb</samp>&rsquo;:
    1102. 

  1102. </p>
    1103. 

  1103. <p>The &lsquo;<samp>blurb</samp>&rsquo; variable is related to the special variable
    1104. 

  1104. &lsquo;<samp>description</samp>&rsquo;.  Its value is made from the first (substantial)
    1105. 

  1105. line of &lsquo;<samp>description</samp>&rsquo;, mentioned as the &quot;brief description&quot;.
    1106. 

  1106. </p>
    1107. 

  1107. <p>The build flags such as &lsquo;<samp>QICFLAGS</samp>&rsquo;, &lsquo;<samp>QICXXFLAGS</samp>&rsquo;,
    1108. 

  1108. &lsquo;<samp>QILDFLAGS</samp>&rsquo;, and &lsquo;<samp>QICPPFLAGS</samp>&rsquo; are only added to the meta file
    1109. 

  1109. if the declared variable &lsquo;<samp>arch</samp>&rsquo; is not equal to the &quot;noarch&quot; value.
    1110. 

  1110. </p>
    1111. 

  1111. <hr>
    1112. 

  1112. <span id="Order-files"></span><div class="header">
    1113. 

  1113. <p>
    1114. 

  1114. Next: <a href="#Creating-packages" accesskey="n" rel="next">Creating packages</a>, Previous: <a href="#Recipes" accesskey="p" rel="prev">Recipes</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Index" title="Index" rel="index">Index</a>]</p>
    1115. 

  1115. </div>
    1116. 

  1116. <span id="Order-files-1"></span><h2 class="chapter">6 Order files</h2>
    1117. 

  1117. <span id="index-handling-build-order"></span>
    1118. 

  1118. 

  1119. <p>The order command has the purpose of resolving the build order through
    1120. 

  1120. .order files.  An order file contains a list of recipe names, by default
    1121. 

  1121. does not perform any action other than to print a resolved list in
    1122. 

  1122. descending order.  For example, if <strong>a</strong> depends on <strong>b</strong> and
    1123. 

  1123. <strong>c</strong>, and <strong>c</strong> depends on <strong>b</strong> as well, the file might
    1124. 

  1124. look like:
    1125. 

  1125. </p>
    1126. 

  1126. <div class="example">
    1127. 

  1127. <pre class="example">a: c b
    1128. 

  1128. b:
    1129. 

  1129. c: b
    1130. 

  1130. </pre></div>
    1131. 

  1131. 

  1132. <p>Each letter represents a recipe name, complete dependencies for
    1133. 

  1133. the first recipe name are listed in descending order, which is
    1134. 

  1134. printed from right to left, and removed from left to right:
    1135. 

  1135. </p>
    1136. 

  1136. <p><small>OUTPUT</small>
    1137. 

  1137. </p>
    1138. 

  1138. <div class="example">
    1139. 

  1139. <pre class="example">b
    1140. 

  1140. c
    1141. 

  1141. a
    1142. 

  1142. </pre></div>
    1143. 

  1143. 

  1144. <p>Blank lines, colons and parentheses are simply ignored.  Comment lines
    1145. 

  1145. beginning with &lsquo;<samp>#</samp>&rsquo; are allowed.
    1146. 

  1146. </p>
    1147. 

  1147. <p>An order file could be used to build a series of packages, for example,
    1148. 

  1148. if the content is:
    1149. 

  1149. </p>
    1150. 

  1150. <div class="example">
    1151. 

  1151. <pre class="example"># Image handling libraries
    1152. 

  1152. 

  1153. libs/libjpeg-turbo: devel/nasm
    1154. 

  1154. x-libs/jasper: libs/libjpeg-turbo
    1155. 

  1155. libs/tiff: libs/libjpeg-turbo
    1156. 

  1156. </pre></div>
    1157. 

  1157. 

  1158. <p>To proceed with each recipe, we can type:
    1159. 

  1159. </p>
    1160. 

  1160. <div class="example">
    1161. 

  1161. <pre class="example">qi order imglibs.order | qi build --install -
    1162. 

  1162. </pre></div>
    1163. 

  1163. 

  1164. <p>The output of &lsquo;<samp>qi order imglibs.order</samp>&rsquo; tells to qi in which order it
    1165. 

  1165. should build the recipes:
    1166. 

  1166. </p>
    1167. 

  1167. <div class="example">
    1168. 

  1168. <pre class="example">devel/nasm
    1169. 

  1169. libs/libjpeg-turbo
    1170. 

  1170. x-libs/jasper
    1171. 

  1171. libs/tiff
    1172. 

  1172. </pre></div>
    1173. 

  1173. 

  1174. 

  1175. <hr>
    1176. 

  1176. <span id="Creating-packages"></span><div class="header">
    1177. 

  1177. <p>
    1178. 

  1178. Next: <a href="#Examining-packages" accesskey="n" rel="next">Examining packages</a>, Previous: <a href="#Order-files" accesskey="p" rel="prev">Order files</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Index" title="Index" rel="index">Index</a>]</p>
    1179. 

  1179. </div>
    1180. 

  1180. <span id="Creating-packages-1"></span><h2 class="chapter">7 Creating packages</h2>
    1181. 

  1181. <span id="index-package-creation"></span>
    1182. 

  1182. 

  1183. <p>The creation command is an internal function of qi to make new Qi
    1184. 

  1184. compatible packages.  A package is produced using the contents of
    1185. 

  1185. the Current Working Directory and the package file is written out.
    1186. 

  1186. </p>
    1187. 

  1187. <div class="example">
    1188. 

  1188. <pre class="example">Usage: qi create [<var>Output/PackageName.tlz</var>]...
    1189. 

  1189. </pre></div>
    1190. 

  1190. 

  1191. <p>The argument for the file name to be written must contain a fully
    1192. 

  1192. qualified named directory as the output directory where the package
    1193. 

  1193. produced will be written.  The file name should be composed using the
    1194. 

  1194. full name: name-version-architecture-release[@pkgcategory].tlz
    1195. 

  1195. </p>
    1196. 

  1196. <p><small>EXAMPLE</small>
    1197. 

  1197. </p>
    1198. 

  1198. <div class="example">
    1199. 

  1199. <pre class="example">cd /usr/pkg
    1200. 

  1200. cd claws-mail_3.17.1_amd64-1@x-apps
    1201. 

  1201. qi create /var/cache/qi/packages/claws-mail_3.17.1_amd64-1@x-apps
    1202. 

  1202. </pre></div>
    1203. 

  1203. 

  1204. <p>In this case, the package &quot;claws-mail_3.17.1_amd64-1@x-apps&quot; will be
    1205. 

  1205. written into &lsquo;<samp>/var/cache/qi/packages/</samp>&rsquo;.
    1206. 

  1206. </p>
    1207. 

  1207. <p>All packages produced are complemented by a checksum file (.sha256).
    1208. 

  1208. </p>
    1209. 

  1209. 

  1210. <hr>
    1211. 

  1211. <span id="Examining-packages"></span><div class="header">
    1212. 

  1212. <p>
    1213. 

  1213. Next: <a href="#Qi-exit-status" accesskey="n" rel="next">Qi exit status</a>, Previous: <a href="#Creating-packages" accesskey="p" rel="prev">Creating packages</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Index" title="Index" rel="index">Index</a>]</p>
    1214. 

  1214. </div>
    1215. 

  1215. <span id="Examining-packages-1"></span><h2 class="chapter">8 Examining packages</h2>
    1216. 

  1216. <span id="index-package-examination"></span>
    1217. 

  1217. 

  1218. <p>The extraction command serves to examine binary packages for debugging
    1219. 

  1219. purposes. It decompresses a package into a single directory, verifying
    1220. 

  1220. its integrity and preserving all of its properties (owner and permissions).
    1221. 

  1221. </p>
    1222. 

  1222. <div class="example">
    1223. 

  1223. <pre class="example">Usage: qi extract [<var>packagename.tlz</var>]...
    1224. 

  1224. </pre></div>
    1225. 

  1225. 

  1226. <p><small>EXAMPLE</small>
    1227. 

  1227. </p>
    1228. 

  1228. <div class="example">
    1229. 

  1229. <pre class="example">qi extract mksh_R56c_amd64-1@shells.tlz
    1230. 

  1230. </pre></div>
    1231. 

  1231. 

  1232. <p>This action will put the content of &quot;mksh_R56c_amd64-1@shells.tlz&quot; into a
    1233. 

  1233. single directory, this is a private directory for the user who requested
    1234. 

  1234. the action, creation operation will be equal to <strong>u=rwx,g=,o= (0700)</strong>.
    1235. 

  1235. The package content will reside on this location, default mask to deploy
    1236. 

  1236. the content will be equal to <strong>u=rwx,g=rwx,o=rwx (0000)</strong>.
    1237. 

  1237. </p>
    1238. 

  1238. <p>Note: the creation of the custom directory is influenced by the value
    1239. 

  1239. of the <code>TMPDIR</code> variable.
    1240. 

  1240. </p>
    1241. 

  1241. 

  1242. <hr>
    1243. 

  1243. <span id="Qi-exit-status"></span><div class="header">
    1244. 

  1244. <p>
    1245. 

  1245. Next: <a href="#Index" accesskey="n" rel="next">Index</a>, Previous: <a href="#Examining-packages" accesskey="p" rel="prev">Examining packages</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Index" title="Index" rel="index">Index</a>]</p>
    1246. 

  1246. </div>
    1247. 

  1247. <span id="Qi-exit-status-1"></span><h2 class="chapter">9 Qi exit status</h2>
    1248. 

  1248. <span id="index-exit-codes"></span>
    1249. 

  1249. 

  1250. <p>All the exit codes are described in this chapter.
    1251. 

  1251. </p>
    1252. 

  1252. <dl compact="compact">
    1253. 

  1253. <dt>&lsquo;<samp>0</samp>&rsquo;</dt>
    1254. 

  1254. <dd><p>Successful completion (no errors).
    1255. 

  1255. </p>
    1256. 

  1256. </dd>
    1257. 

  1257. <dt>&lsquo;<samp>1</samp>&rsquo;</dt>
    1258. 

  1258. <dd><p>Minor common errors:
    1259. 

  1259. </p>
    1260. 

  1260. <ul>
    1261. 

  1261. <li> Help usage on invalid options or required arguments.
    1262. 

  1262. 

  1263. </li><li> Program needed by qi (prerequisite) is not available.
    1264. 

  1264. </li></ul>
    1265. 

  1265. 

  1266. </dd>
    1267. 

  1267. <dt>&lsquo;<samp>2</samp>&rsquo;</dt>
    1268. 

  1268. <dd><p>Command execution error:
    1269. 

  1269. </p>
    1270. 

  1270. <p>This code is used to return the evaluation of an external command or shell
    1271. 

  1271. arguments in case of failure.
    1272. 

  1272. </p>
    1273. 

  1273. </dd>
    1274. 

  1274. <dt>&lsquo;<samp>3</samp>&rsquo;</dt>
    1275. 

  1275. <dd><p>Integrity check error for compressed files.
    1276. 

  1276. </p>
    1277. 

  1277. <p>Compressed files means:
    1278. 

  1278. </p>
    1279. 

  1279. <ul>
    1280. 

  1280. <li> A tarball file from tar(1), typically handled by the GNU tar implementation.
    1281. 

  1281. Supported extensions: .tar, .tar.gz, .tgz, .tar.Z, .tar.bz2, .tbz2, .tbz,
    1282. 

  1282. .tar.xz, .txz, .tar.zst, .tzst
    1283. 

  1283. 

  1284. </li><li> A tarball file from tarlz(1).
    1285. 

  1285. Supported extensions: .tar.lz, .tlz
    1286. 

  1286. 

  1287. </li><li> Zip files from unzip(1).
    1288. 

  1288. Supported extensions: .zip, .ZIP
    1289. 

  1289. 

  1290. </li><li> Gzip files from gzip(1).
    1291. 

  1291. Supported extensions: .gz, .Z
    1292. 

  1292. 

  1293. </li><li> Bzip2 files from bzip2(1).
    1294. 

  1294. Supported extension: .bz2
    1295. 

  1295. 

  1296. </li><li> Lzip files from lzip(1).
    1297. 

  1297. Supported extension: .lz
    1298. 

  1298. 

  1299. </li><li> Xz files from xz(1).
    1300. 

  1300. Supported extension: .xz
    1301. 

  1301. 

  1302. </li><li> Zstd files from zstd(1).
    1303. 

  1303. Supported extension: .zst
    1304. 

  1304. </li></ul>
    1305. 

  1305. 

  1306. </dd>
    1307. 

  1307. <dt>&lsquo;<samp>4</samp>&rsquo;</dt>
    1308. 

  1308. <dd><p>File empty, not regular, or expected.
    1309. 

  1309. </p>
    1310. 

  1310. <p>It&rsquo;s commonly expected:
    1311. 

  1311. </p>
    1312. 

  1312. <ul>
    1313. 

  1313. <li> An argument for giving commands.
    1314. 

  1314. 

  1315. </li><li> A regular file or readable directory.
    1316. 

  1316. 

  1317. </li><li> An expected extension: .tlz, .sha256, .order.
    1318. 

  1318. 

  1319. </li><li> A protocol supported by the network downloader tool.
    1320. 

  1320. </li></ul>
    1321. 

  1321. 

  1322. </dd>
    1323. 

  1323. <dt>&lsquo;<samp>5</samp>&rsquo;</dt>
    1324. 

  1324. <dd><p>Empty or not defined variable:
    1325. 

  1325. </p>
    1326. 

  1326. <p>This code is used to report empty or undefined variables (usually
    1327. 

  1327. variables coming from a recipe or assigned arrays that are tested).
    1328. 

  1328. </p>
    1329. 

  1329. </dd>
    1330. 

  1330. <dt>&lsquo;<samp>6</samp>&rsquo;</dt>
    1331. 

  1331. <dd><p>Package already installed:
    1332. 

  1332. </p>
    1333. 

  1333. <p>The package directory for an incoming .tlz package already exists.
    1334. 

  1334. </p>
    1335. 

  1335. </dd>
    1336. 

  1336. <dt>&lsquo;<samp>10</samp>&rsquo;</dt>
    1337. 

  1337. <dd><p>Network manager error:
    1338. 

  1338. </p>
    1339. 

  1339. <p>This code is used if the network downloader tool fails for some reason.
    1340. 

  1340. </p></dd>
    1341. 

  1341. </dl>
    1342. 

  1342. 

  1343. 

  1344. <hr>
    1345. 

  1345. <span id="Index"></span><div class="header">
    1346. 

  1346. <p>
    1347. 

  1347. Previous: <a href="#Qi-exit-status" accesskey="p" rel="prev">Qi exit status</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Index" title="Index" rel="index">Index</a>]</p>
    1348. 

  1348. </div>
    1349. 

  1349. <span id="Index-1"></span><h2 class="unnumbered">Index</h2>
    1350. 

  1350. 

  1351. <table><tr><th valign="top">Jump to: &nbsp; </th><td><a class="summary-letter" href="#Index_cp_letter-C"><b>C</b></a>
    1352. 

  1352.  &nbsp; 
    1353. 

  1353. <a class="summary-letter" href="#Index_cp_letter-E"><b>E</b></a>
    1354. 

  1354.  &nbsp; 
    1355. 

  1355. <a class="summary-letter" href="#Index_cp_letter-H"><b>H</b></a>
    1356. 

  1356.  &nbsp; 
    1357. 

  1357. <a class="summary-letter" href="#Index_cp_letter-I"><b>I</b></a>
    1358. 

  1358.  &nbsp; 
    1359. 

  1359. <a class="summary-letter" href="#Index_cp_letter-M"><b>M</b></a>
    1360. 

  1360.  &nbsp; 
    1361. 

  1361. <a class="summary-letter" href="#Index_cp_letter-P"><b>P</b></a>
    1362. 

  1362.  &nbsp; 
    1363. 

  1363. <a class="summary-letter" href="#Index_cp_letter-R"><b>R</b></a>
    1364. 

  1364.  &nbsp; 
    1365. 

  1365. <a class="summary-letter" href="#Index_cp_letter-S"><b>S</b></a>
    1366. 

  1366.  &nbsp; 
    1367. 

  1367. <a class="summary-letter" href="#Index_cp_letter-T"><b>T</b></a>
    1368. 

  1368.  &nbsp; 
    1369. 

  1369. <a class="summary-letter" href="#Index_cp_letter-V"><b>V</b></a>
    1370. 

  1370.  &nbsp; 
    1371. 

  1371. <a class="summary-letter" href="#Index_cp_letter-W"><b>W</b></a>
    1372. 

  1372.  &nbsp; 
    1373. 

  1373. </td></tr></table>
    1374. 

  1374. <table class="index-cp" border="0">
    1375. 

  1375. <tr><td></td><th align="left">Index Entry</th><td>&nbsp;</td><th align="left"> Section</th></tr>
    1376. 

  1376. <tr><td colspan="4"> <hr></td></tr>
    1377. 

  1377. <tr><th id="Index_cp_letter-C">C</th><td></td><td></td></tr>
    1378. 

  1378. <tr><td></td><td valign="top"><a href="#index-configuration-file">configuration file</a>:</td><td>&nbsp;</td><td valign="top"><a href="#The-qirc-file">The qirc file</a></td></tr>
    1379. 

  1379. <tr><td colspan="4"> <hr></td></tr>
    1380. 

  1380. <tr><th id="Index_cp_letter-E">E</th><td></td><td></td></tr>
    1381. 

  1381. <tr><td></td><td valign="top"><a href="#index-environment-variables">environment variables</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Recipes">Recipes</a></td></tr>
    1382. 

  1382. <tr><td></td><td valign="top"><a href="#index-exit-codes">exit codes</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Qi-exit-status">Qi exit status</a></td></tr>
    1383. 

  1383. <tr><td colspan="4"> <hr></td></tr>
    1384. 

  1384. <tr><th id="Index_cp_letter-H">H</th><td></td><td></td></tr>
    1385. 

  1385. <tr><td></td><td valign="top"><a href="#index-handling-build-order">handling build order</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Order-files">Order files</a></td></tr>
    1386. 

  1386. <tr><td colspan="4"> <hr></td></tr>
    1387. 

  1387. <tr><th id="Index_cp_letter-I">I</th><td></td><td></td></tr>
    1388. 

  1388. <tr><td></td><td valign="top"><a href="#index-introduction-to-qi">introduction to qi</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Introduction-to-Qi">Introduction to Qi</a></td></tr>
    1389. 

  1389. <tr><td></td><td valign="top"><a href="#index-invocation">invocation</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Invoking-qi">Invoking qi</a></td></tr>
    1390. 

  1390. <tr><td colspan="4"> <hr></td></tr>
    1391. 

  1391. <tr><th id="Index_cp_letter-M">M</th><td></td><td></td></tr>
    1392. 

  1392. <tr><td></td><td valign="top"><a href="#index-managing-packages">managing packages</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Packages">Packages</a></td></tr>
    1393. 

  1393. <tr><td colspan="4"> <hr></td></tr>
    1394. 

  1394. <tr><th id="Index_cp_letter-P">P</th><td></td><td></td></tr>
    1395. 

  1395. <tr><td></td><td valign="top"><a href="#index-package-blacklist">package blacklist</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Packages">Packages</a></td></tr>
    1396. 

  1396. <tr><td></td><td valign="top"><a href="#index-package-build">package build</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Recipes">Recipes</a></td></tr>
    1397. 

  1397. <tr><td></td><td valign="top"><a href="#index-package-conflicts">package conflicts</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Packages">Packages</a></td></tr>
    1398. 

  1398. <tr><td></td><td valign="top"><a href="#index-package-creation">package creation</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Creating-packages">Creating packages</a></td></tr>
    1399. 

  1399. <tr><td></td><td valign="top"><a href="#index-package-de_002dinstallation">package de-installation</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Packages">Packages</a></td></tr>
    1400. 

  1400. <tr><td></td><td valign="top"><a href="#index-package-examination">package examination</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Examining-packages">Examining packages</a></td></tr>
    1401. 

  1401. <tr><td></td><td valign="top"><a href="#index-package-installation">package installation</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Packages">Packages</a></td></tr>
    1402. 

  1402. <tr><td></td><td valign="top"><a href="#index-package-upgrade">package upgrade</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Packages">Packages</a></td></tr>
    1403. 

  1403. <tr><td colspan="4"> <hr></td></tr>
    1404. 

  1404. <tr><th id="Index_cp_letter-R">R</th><td></td><td></td></tr>
    1405. 

  1405. <tr><td></td><td valign="top"><a href="#index-recipes">recipes</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Recipes">Recipes</a></td></tr>
    1406. 

  1406. <tr><td colspan="4"> <hr></td></tr>
    1407. 

  1407. <tr><th id="Index_cp_letter-S">S</th><td></td><td></td></tr>
    1408. 

  1408. <tr><td></td><td valign="top"><a href="#index-special-variables">special variables</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Recipes">Recipes</a></td></tr>
    1409. 

  1409. <tr><td colspan="4"> <hr></td></tr>
    1410. 

  1410. <tr><th id="Index_cp_letter-T">T</th><td></td><td></td></tr>
    1411. 

  1411. <tr><td></td><td valign="top"><a href="#index-the-meta-file">the meta file</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Recipes">Recipes</a></td></tr>
    1412. 

  1412. <tr><td colspan="4"> <hr></td></tr>
    1413. 

  1413. <tr><th id="Index_cp_letter-V">V</th><td></td><td></td></tr>
    1414. 

  1414. <tr><td></td><td valign="top"><a href="#index-variables">variables</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Recipes">Recipes</a></td></tr>
    1415. 

  1415. <tr><td colspan="4"> <hr></td></tr>
    1416. 

  1416. <tr><th id="Index_cp_letter-W">W</th><td></td><td></td></tr>
    1417. 

  1417. <tr><td></td><td valign="top"><a href="#index-writing-recipes">writing recipes</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Recipes">Recipes</a></td></tr>
    1418. 

  1418. <tr><td colspan="4"> <hr></td></tr>
    1419. 

  1419. </table>
    1420. 

  1420. <table><tr><th valign="top">Jump to: &nbsp; </th><td><a class="summary-letter" href="#Index_cp_letter-C"><b>C</b></a>
    1421. 

  1421.  &nbsp; 
    1422. 

  1422. <a class="summary-letter" href="#Index_cp_letter-E"><b>E</b></a>
    1423. 

  1423.  &nbsp; 
    1424. 

  1424. <a class="summary-letter" href="#Index_cp_letter-H"><b>H</b></a>
    1425. 

  1425.  &nbsp; 
    1426. 

  1426. <a class="summary-letter" href="#Index_cp_letter-I"><b>I</b></a>
    1427. 

  1427.  &nbsp; 
    1428. 

  1428. <a class="summary-letter" href="#Index_cp_letter-M"><b>M</b></a>
    1429. 

  1429.  &nbsp; 
    1430. 

  1430. <a class="summary-letter" href="#Index_cp_letter-P"><b>P</b></a>
    1431. 

  1431.  &nbsp; 
    1432. 

  1432. <a class="summary-letter" href="#Index_cp_letter-R"><b>R</b></a>
    1433. 

  1433.  &nbsp; 
    1434. 

  1434. <a class="summary-letter" href="#Index_cp_letter-S"><b>S</b></a>
    1435. 

  1435.  &nbsp; 
    1436. 

  1436. <a class="summary-letter" href="#Index_cp_letter-T"><b>T</b></a>
    1437. 

  1437.  &nbsp; 
    1438. 

  1438. <a class="summary-letter" href="#Index_cp_letter-V"><b>V</b></a>
    1439. 

  1439.  &nbsp; 
    1440. 

  1440. <a class="summary-letter" href="#Index_cp_letter-W"><b>W</b></a>
    1441. 

  1441.  &nbsp; 
    1442. 

  1442. </td></tr></table>
    1443. 

  1443. 

  1444. <div class="footnote">
    1445. 

  1445. <hr>
    1446. 

  1446. <h4 class="footnotes-heading">Footnotes</h4>
    1447. 

  1447. 

  1448. <h5><a id="FOOT1" href="#DOCF1">(1)</a></h3>
    1449. 

  1449. <p>For more details about tarlz and the
    1450. 

  1450. lzip format, visit <a href="https://lzip.nongnu.org/tarlz.html">https://lzip.nongnu.org/tarlz.html</a>.</p>
    1451. 

  1451. <h5><a id="FOOT2" href="#DOCF2">(2)</a></h3>
    1452. 

  1452. <p>The official guide for Graft can be found at
    1453. 

  1453. <a href="https://peters.gormand.com.au/Home/tools/graft/graft.html">https://peters.gormand.com.au/Home/tools/graft/graft.html</a>.</p>
    1454. 

  1454. <h5><a id="FOOT3" href="#DOCF3">(3)</a></h3>
    1455. 

  1455. <p>About the &lsquo;<samp>--bsolid</samp>&rsquo; granularity option of tarlz(1),
    1456. 

  1456. <a href="https://www.nongnu.org/lzip/manual/tarlz_manual.html#g_t_002d_002dbsolid">https://www.nongnu.org/lzip/manual/tarlz_manual.html#g_t_002d_002dbsolid</a>.</p>
    1457. 

  1457. <h5><a id="FOOT4" href="#DOCF4">(4)</a></h3>
    1458. 

  1458. <p>The proposal for &lsquo;<samp>license</samp>&rsquo; was made by Richard M. Stallman at
    1459. 

  1459. <a href="https://lists.gnu.org/archive/html/gnu-linux-libre/2016-05/msg00003.html">https://lists.gnu.org/archive/html/gnu-linux-libre/2016-05/msg00003.html</a>.</p>
    1460. 

  1460. </div>
    1461. 

  1461. <hr>
    1462. 

  1462. 

  1463. 

  1464. 

  1465. </body>
    1466. 

  1466. </html>
    1467. 

  1467.