summaryrefslogtreecommitdiffstats
path: root/slackbook/html/package-management-making-tags-and-tagfiles.html
diff options
context:
space:
mode:
Diffstat (limited to 'slackbook/html/package-management-making-tags-and-tagfiles.html')
-rw-r--r--slackbook/html/package-management-making-tags-and-tagfiles.html136
1 files changed, 0 insertions, 136 deletions
diff --git a/slackbook/html/package-management-making-tags-and-tagfiles.html b/slackbook/html/package-management-making-tags-and-tagfiles.html
deleted file mode 100644
index 9c82bdf0..00000000
--- a/slackbook/html/package-management-making-tags-and-tagfiles.html
+++ /dev/null
@@ -1,136 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta name="generator" content="HTML Tidy, see www.w3.org" />
-<title>Making Tags and Tagfiles (for setup)</title>
-<meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.7" />
-<link rel="HOME" title="Slackware Linux Essentials" href="index.html" />
-<link rel="UP" title="Slackware Package Management" href="package-management.html" />
-<link rel="PREVIOUS" title="Making Packages"
-href="package-management-making-packages.html" />
-<link rel="NEXT" title="ZipSlack" href="zipslack.html" />
-<link rel="STYLESHEET" type="text/css" href="docbook.css" />
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-</head>
-<body class="SECT1" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#840084"
-alink="#0000FF">
-<div class="NAVHEADER">
-<table summary="Header navigation table" width="100%" border="0" cellpadding="0"
-cellspacing="0">
-<tr>
-<th colspan="3" align="center">Slackware Linux Essentials</th>
-</tr>
-
-<tr>
-<td width="10%" align="left" valign="bottom"><a
-href="package-management-making-packages.html" accesskey="P">Prev</a></td>
-<td width="80%" align="center" valign="bottom">Chapter 18 Slackware Package
-Management</td>
-<td width="10%" align="right" valign="bottom"><a href="zipslack.html"
-accesskey="N">Next</a></td>
-</tr>
-</table>
-
-<hr align="LEFT" width="100%" />
-</div>
-
-<div class="SECT1">
-<h1 class="SECT1"><a id="PACKAGE-MANAGEMENT-MAKING-TAGS-AND-TAGFILES"
-name="PACKAGE-MANAGEMENT-MAKING-TAGS-AND-TAGFILES">18.4 Making Tags and Tagfiles (for
-setup)</a></h1>
-
-<p>The Slackware setup program handles installation of the software packages on your
-system. There are files that tell the setup program which packages must be installed,
-which ones are optional, and which ones are selected by default by the setup program.</p>
-
-<p>A tagfile is in the first software series directory and is called tagfile. It lists
-the packages in that particular disk set and their status. The status can be:</p>
-
-<div class="TABLE"><a id="AEN6621" name="AEN6621"></a>
-<p><b>Table 18-3. Tagfile Status Options</b></p>
-
-<table border="0" frame="void" width="100%" class="CALSTABLE">
-<col width="25%" />
-<col width="75%" />
-<thead>
-<tr>
-<th>Option</th>
-<th>Meaning</th>
-</tr>
-</thead>
-
-<tbody>
-<tr>
-<td>ADD</td>
-<td>The package is required for proper system operation</td>
-</tr>
-
-<tr>
-<td>SKP</td>
-<td>The package will be automatically skipped</td>
-</tr>
-
-<tr>
-<td>REC</td>
-<td>The package is not required, but recommended</td>
-</tr>
-
-<tr>
-<td>OPT</td>
-<td>The package is optional</td>
-</tr>
-</tbody>
-</table>
-</div>
-
-<p>The format is simply:</p>
-
-<table border="0" bgcolor="#E0E0E0" width="100%">
-<tr>
-<td>
-<pre class="SCREEN">
-package_name: status
-</pre>
-</td>
-</tr>
-</table>
-
-<p>One package per line. The original tagfiles for each software series are stored as
-tagfile.org. So if you mess up yours, you can restore the original one.</p>
-
-<p>Many administrators prefer writing their own tagfiles and starting the installer and
-selecting &#8220;full&#8221;. The setup program will read the tagfiles and perform the
-installation according to their contents. If you use REC or OPT, a dialog box will be
-presented to the user asking whether or not they want a particular package. Therefore, it
-is recommended that you stick with ADD and SKP when writing tagfiles for automated
-installs.</p>
-
-<p>Just make sure your tagfiles are written to the same location as the originals. Or you
-can specify a custom tagfile path if you have custom tagfiles.</p>
-</div>
-
-<div class="NAVFOOTER">
-<hr align="LEFT" width="100%" />
-<table summary="Footer navigation table" width="100%" border="0" cellpadding="0"
-cellspacing="0">
-<tr>
-<td width="33%" align="left" valign="top"><a
-href="package-management-making-packages.html" accesskey="P">Prev</a></td>
-<td width="34%" align="center" valign="top"><a href="index.html"
-accesskey="H">Home</a></td>
-<td width="33%" align="right" valign="top"><a href="zipslack.html"
-accesskey="N">Next</a></td>
-</tr>
-
-<tr>
-<td width="33%" align="left" valign="top">Making Packages</td>
-<td width="34%" align="center" valign="top"><a href="package-management.html"
-accesskey="U">Up</a></td>
-<td width="33%" align="right" valign="top">ZipSlack</td>
-</tr>
-</table>
-</div>
-</body>
-</html>
-