diff options
Diffstat (limited to 'source/a/pkgtools/manpages')
| -rw-r--r-- | source/a/pkgtools/manpages/explodepkg.8 | 41 | ||||
| -rw-r--r-- | source/a/pkgtools/manpages/installpkg.8 | 91 | ||||
| -rw-r--r-- | source/a/pkgtools/manpages/makepkg.8 | 135 | ||||
| -rw-r--r-- | source/a/pkgtools/manpages/pkgtool.8 | 95 | ||||
| -rw-r--r-- | source/a/pkgtools/manpages/removepkg.8 | 108 | ||||
| -rw-r--r-- | source/a/pkgtools/manpages/setup.8-deprecated | 120 | ||||
| -rw-r--r-- | source/a/pkgtools/manpages/upgradepkg.8 | 98 |
7 files changed, 688 insertions, 0 deletions
diff --git a/source/a/pkgtools/manpages/explodepkg.8 b/source/a/pkgtools/manpages/explodepkg.8 new file mode 100644 index 000000000..3e11fddc8 --- /dev/null +++ b/source/a/pkgtools/manpages/explodepkg.8 @@ -0,0 +1,41 @@ +.\" -*- nroff -*- +.ds g \" empty +.ds G \" empty +.\" Like TP, but if specified indent is more than half +.\" the current line-length - indent, use the default indent. +.de Tp +.ie \\n(.$=0:((0\\$1)*2u>(\\n(.lu-\\n(.iu)) .TP +.el .TP "\\$1" +.. +.TH EXPLODEPKG 8 "21 May 1994" "Slackware Version 2.0.0" +.SH NAME +explodepkg \- Extract the contents of a tar+compression package (such as a Slackware +software package) in the current directory. +.SH SYNOPSIS +.B explodepkg +.BI package +.BI [ +.BI package2, +.BI package3, +.BI ... +.BI ] +.SH DESCRIPTION +.B explodepkg +uncompresses and untars Slackware *.tgz (or .tbz, .tlz, .txz) packages (or any archive +that was created by +compressing a tarfile with one of the supported compression utilities) in the current directory. It is not usually +used to install packages, since it doesn't execute the installation scripts +in ./install or ./var/log/setup. The primary use for +.B explodepkg +is in package maintenance - exploding a package in a subdirectory, making fixes +to it or upgrading the software, and then building the updated package with +.B makepkg. +.SH AUTHOR +Patrick J. Volkerding <volkerdi@slackware.com> +.SH "SEE ALSO" +.BR tar(1), +.BR gzip(1), +.BR installpkg(8), +.BR makepkg(8), +.BR pkgtool(8), +.BR upgradepkg(8) diff --git a/source/a/pkgtools/manpages/installpkg.8 b/source/a/pkgtools/manpages/installpkg.8 new file mode 100644 index 000000000..2d77f10e7 --- /dev/null +++ b/source/a/pkgtools/manpages/installpkg.8 @@ -0,0 +1,91 @@ +.\" -*- nroff -*- +.ds g \" empty +.ds G \" empty +.\" Like TP, but if specified indent is more than half +.\" the current line-length - indent, use the default indent. +.de Tp +.ie \\n(.$=0:((0\\$1)*2u>(\\n(.lu-\\n(.iu)) .TP +.el .TP "\\$1" +.. +.TH INSTALLPKG 8 "22 Nov 2001" "Slackware Version 8.1.0" +.SH NAME +installpkg \- install Slackware packages. +.SH SYNOPSIS +.B installpkg +[ +.B \--warn +] +[ +.B \--md5sum +] +[ +.B \--root /otherroot +] +[ +.B \--infobox +] +[ +.B \--menu +] +[ +.B \--ask +] +[ +.B \--priority ADD|REC|OPT|SKP +] +[ +.B \--tagfile /somedir/tagfile +] +.BI packagename +[ +.B packagename2 ... +] +.SH DESCRIPTION +.B installpkg +installs single or multiple *.tgz (or .tbz, .tlz, .txz) binary packages designed +for use with the Slackware Linux distribution onto your system. +.SH OPTIONS +.TP +.B \--warn packagename +Generate a report to the standard output about which files and directories +would be removed or overwritten if you install the package, but do not +actually install it. +.TP +.B \--md5sum packagename +Record the package md5sum in the metadata written in /var/log/packages. +.TP +.B \--root /otherroot +Install using a location other than / (the default) as the root of the +filesystem to install on. In the example given, use /otherroot instead. Setting +the ROOT environment variable does the same thing. +.TP +.B \--infobox +Use /bin/dialog to display an informational dialog as the package is installed. +Primarily used when installpkg is called from other scripts. +.TP +.B \--menu +Use /bin/dialog to display a menu asking the user if they would like to install the +package(s) or not. Generally used when installpkg is called from other scripts. +.TP +.B \--ask +Used with -menu mode. When selected, always ask if a package should be +installed regardless of what the package's priority is. +.TP +.B \--priority ADD|REC|OPT|SKP +When installing with the \-menu option, package priority levels (found in the file +"tagfile" in the package directory) are used to automatically install (ADD) or +skip (SKP) a package, or to suggest recommended (REC) or optional (OPT) to the user +if a menu is displayed. If a priority is set on the command line, it will override +the values set in the tagfile for the entire package list. +.TP +.B \--tagfile /somedir/tagfile +Specify a different file to use for package priorities (in this example, /somedir/tagfile +will be used). The default is "tagfile" in the package's directory. +.SH AUTHOR +Patrick J. Volkerding <volkerdi@slackware.com> +.SH "SEE ALSO" +.BR makepkg(8), +.BR removepkg(8), +.BR explodepkg(8), +.BR pkgtool(8), +.BR upgradepkg(8) diff --git a/source/a/pkgtools/manpages/makepkg.8 b/source/a/pkgtools/manpages/makepkg.8 new file mode 100644 index 000000000..b280ce51f --- /dev/null +++ b/source/a/pkgtools/manpages/makepkg.8 @@ -0,0 +1,135 @@ +.\" -*- nroff -*- +.ds g \" empty +.ds G \" empty +.\" Like TP, but if specified indent is more than half +.\" the current line-length - indent, use the default indent. +.de Tp +.ie \\n(.$=0:((0\\$1)*2u>(\\n(.lu-\\n(.iu)) .TP +.el .TP "\\$1" +.. +.TH MAKEPKG 8 "21 May 1994" "Slackware Version 2.0.0" +.SH NAME +makepkg \- make Slackware packages. +.SH SYNOPSIS +.B makepkg +[ +.B -l, --linkadd y|n +] +[ +.B -c, --chown y|n +] +.BI packagename +.SH DESCRIPTION +.B makepkg +creates a new Slackware compatible package. +The package is constructed using the contents of the current directory and +all subdirectories. If symbolic links exist, they will be converted to script +code to recreate them when the package is installed. This code will be +appended to the primary installation script +.B ( install/doinst.sh ) +, or, if that script does not exist it will be created with those contents. +The package will be written out to the file +.BI packagename +which should be the full name, including the extension. This is usually .tgz, +but .tbz, .tlz, and .txz are also accepted. The proper compression utility +(gzip, bzip2, lzma, or xz) needs to be installed on the machine. +.SH OPTIONS +.TP +.B \-l, --linkadd y|n +If y, add any symbolic links found to the install script (doinst.sh) and +delete them. This is the recommended action. If this option is not used, +makepkg will prompt if symbolic links are found. +.TP +.B \-p, --prepend +If this option is given, then any symbolic links added to doinst.sh will be +prepended to the existing script. This is useful for packages that contain +shared libraries that need to be linked first because programs will use them +later in the doinst.sh script. +.TP +.B \-c, --chown y|n +If y, makepkg will reset all directory permissions to 755 and ownership to root:root. +In general, you should have the permissions and ownerships worked out yourself, so +relying on setting this option to y is somewhat sloppy. It is not the default. If an +option is not provided, makepkg will prompt. +.SH INSTALLATION SCRIPTS +There are 3 types of installation scripts supported in the Slackware package +system. +.TP +The first is the +.B primary +installation script. This is found in the subdirectory +.B ./install +and must have the name +.B doinst.sh +in order to be recognized. This ( and other install scripts ) should be written +using the basic Bourne shell syntax recognized by the +.B ash +shell, since this is the shell that will be used to execute the script when +installing from a Slackware install floppy. This is a common trap - beware of +using +.B bash +syntax extensions, because the script will work fine when installed from the +hard drive, but will bomb out when installed from floppy. If the package is +for personal use, this isn't a problem. Be careful, though, if you plan to +share your package with other users. The +.B primary installation script +is executed immediately after the package is installed with +.B installpkg, pkgtool, +or +.B setup. +.TP +The second type of script is the +.B configuration +script. This is found in the subdirectory +.B ./var/log/setup +and must have a name that starts with +.B setup. +in order to be recongnized. An example is the timezone script: +.B /var/log/setup/setup.timeconfig. +These scripts are executed during the +.B CONFIGURE +phase of +.B setup, +and are re-executed each time the user runs the +.B CONFIGURE +option from +.B setup +from then on. +Typically, the user will go through this phase of setup following the +installation of all the packages. Anything that needs to be interactive +should go in one of these scripts to avoid halting the package installation +process during +.B setup. +.TP +The third type of script is the +.B onlyonce +script. Like the name suggests, these are executed only once after the package +is installed, in contrast to the standard +.B configuration +script. These scripts are also found in the +.B ./var/log/setup +directory and must have a name that starts with +.B setup., +but in addition the name must contain the string +.B onlyonce. +An example might be a script with the name +.B /var/log/setup/setup.onlyonce.testscript +.SH PACKAGE FORMAT +.B makepkg +uses GNU tar plus GNU gzip to create its packages. A simple way to +extract the contents of a package (without executing the installation +scripts, of course) is to use a command like this: +.TP +explodepkg package.tgz +.TP +Or, something like this: +.TP +gzip -dc package.tgz | tar xvvf - +.SH AUTHOR +Patrick J. Volkerding <volkerdi@slackware.com> +.SH "SEE ALSO" +.BR installpkg(8), +.BR explodepkg(8), +.BR removepkg(8), +.BR pkgtool(8), +.BR upgradepkg(8) diff --git a/source/a/pkgtools/manpages/pkgtool.8 b/source/a/pkgtools/manpages/pkgtool.8 new file mode 100644 index 000000000..56e392176 --- /dev/null +++ b/source/a/pkgtools/manpages/pkgtool.8 @@ -0,0 +1,95 @@ +.\" -*- nroff -*- +.ds g \" empty +.ds G \" empty +.\" Like TP, but if specified indent is more than half +.\" the current line-length - indent, use the default indent. +.de Tp +.ie \\n(.$=0:((0\\$1)*2u>(\\n(.lu-\\n(.iu)) .TP +.el .TP "\\$1" +.. +.TH PKGTOOL 8 "24 Nov 1995" "Slackware Version 3.1.0" +.SH NAME +pkgtool \- software package maintenance tool. +.SH SYNOPSIS +.B pkgtool +.LP +.B pkgtool +[ +.B --sets #a#b#c# +] +[ +.B --source_mounted +] +[ +.B --ignore_tagfiles +] +[ +.B --tagfile tagfile +] +[ +.B --source_dir directory +] +[ +.B --target_dir directory +] +[ +.B --source_device device +] +.SH DESCRIPTION +.B pkgtool +is a menu-driven package maintenance tool provided with the Slackware Linux +distribution. It allows the user to install, remove, or view +software packages through an interactive +system. Pkgtool can also be used to re-run the menu-driven scripts normally +executed at the end of a Slackware installation. This is useful for doing +basic reconfiguration (like changing the mouse type). +.SH OPTIONS +Most users will not want to use any options when running +.B pkgtool. +These are generally used only when +.B pkgtool +is run during the initial system installation. +Feel free to try them, but be careful. +.TP +.B \--sets #A#B#C# +Install the disk sets A, B, C. Seperate the disk set names by '#' symbols. +.TP +.B \--source_mounted +When this flag is present, +.B pkgtool +will not attempt to unmount and remount the source device with each disk. +.TP +.B \--ignore_tagfiles +When this flag is present, +.B pkgtool +will install every package encountered no matter what the tagfiles say. +.TP +.B \--tagfile tagfile +This flag is used to specify from the command line which tagfile should be +used for the installation. +.TP +.B \--source_dir directory +Used when installing multiple packages from disk sets. This is the directory +in which the subdirectories for each disk are found. This isn't used when +installing from floppy. +.TP +.B \--target_dir directory +The directory where the target root directory is located. This is '/' when +installing on the hard drive, or typically '/mnt' when installing from an +install disk. +.TP +.B \--source_device device +The source device to install from. This is not used if you've provided the +.B \--source_mounted +flag. It's usually used when installing from floppy, as in: + \--source_device /dev/fd0u1440 +or + \--source_device /dev/fd1h1200. +.SH AUTHOR +Patrick J. Volkerding <volkerdi@slackware.com> +.SH "SEE ALSO" +.BR makepkg(8), +.BR explodepkg(8), +.BR installpkg(8), +.BR removepkg(8), +.BR upgradepkg(8) diff --git a/source/a/pkgtools/manpages/removepkg.8 b/source/a/pkgtools/manpages/removepkg.8 new file mode 100644 index 000000000..3bd8bf7a7 --- /dev/null +++ b/source/a/pkgtools/manpages/removepkg.8 @@ -0,0 +1,108 @@ +.\" -*- nroff -*- +.ds g \" empty +.ds G \" empty +.\" Like TP, but if specified indent is more than half +.\" the current line-length - indent, use the default indent. +.de Tp +.ie \\n(.$=0:((0\\$1)*2u>(\\n(.lu-\\n(.iu)) .TP +.el .TP "\\$1" +.. +.TH REMOVEPKG 8 "23 Nov 2001" "Slackware Version 8.1.0" +.SH NAME +removepkg \- remove Slackware packages. +.SH SYNOPSIS +.B removepkg +.BI packagename +.LP +[ +.B ROOT=/mnt +] +.B removepkg +[ +.B \-copy +] +[ +.B \-keep +] +[ +.B \-preserve +] +[ +.B \-warn +] +.BI packagename +.SH DESCRIPTION +.B removepkg +removes a previously installed Slackware package, while writing a progress +report to the standard output. A package may be specified either by the +full package name (as you'd see listed in /var/log/packages/), or by the +base package name. For example, the package foo-1.0-i486-1.tgz may be removed +with any of the following commands: + +removepkg foo-1.0-i486-1.tgz (also recognized: .tbz, .tlz, .txz) + +removepkg foo-1.0-i486-1 + +removepkg foo.tgz + +removepkg foo + +When deleting files, +.B removepkg +will analyze the contents of the other packages installed on your system, and +will only delete the files that are unique to the package being removed. +Similarly, the installation scripts for all the other packages will be +considered when deciding whether or not to delete symbolic links from the +package. +.LP +Removing a package (as well as installing one) can be a dangerous undertaking. +For this reason, there is the +.B \-warn +option available. When you use this, +.B removepkg +will not actually remove any files or links, but will output a detailed report +of what it would do if you actually did remove the package. It's suggested that +you do this (and maybe pipe the output to +.B less +) before removing packages to make sure you've backed up anything that might +be important. +.LP +When removing a package, it's original file index will be moved from +/var/log/packages to /var/log/removed_packages. Likewise, it's installation +script will be moved from /var/log/scripts to /var/log/removed_scripts. +.SH OPTIONS +.TP +.B \-warn packagename +Generate a report to the standard output about which files and directories +would be removed, but does not actually remove the package. +.TP +.B \-preserve packagename +If specified, the complete package subtree is reconstructed in +/var/log/setup/tmp/preserved_packages/packagename. +.TP +.B \-copy packagename +Construct a copy of the package under /var/log/setup/tmp/preserved_packages/packagename, +but don't remove it. (same effect as \-warn \-preserve) +.TP +.B \-keep +Save the intermediate files created by removepkg (delete_list, +required_files, uniq_list, del_link_list, required_links, +required_list). Mostly useful for debugging purposes. +.SH " " +It's possible to remove a package from a filesystem +other than / by supplying +.B removepkg +with a +.B ROOT +environment variable: +.TP +.B ROOT=/mnt removepkg package + +.SH AUTHORS +Patrick J. Volkerding <volkerdi@slackware.com>, +with enhancements by Christian Franke <c.franke@acm.org> +.SH "SEE ALSO" +.BR installpkg(8), +.BR makepkg(8), +.BR pkgtool(8), +.BR upgradepkg(8) diff --git a/source/a/pkgtools/manpages/setup.8-deprecated b/source/a/pkgtools/manpages/setup.8-deprecated new file mode 100644 index 000000000..533974222 --- /dev/null +++ b/source/a/pkgtools/manpages/setup.8-deprecated @@ -0,0 +1,120 @@ +.\" -*- nroff -*- +.ds g \" empty +.ds G \" empty +.\" Like TP, but if specified indent is more than half +.\" the current line-length - indent, use the default indent. +.de Tp +.ie \\n(.$=0:((0\\$1)*2u>(\\n(.lu-\\n(.iu)) .TP +.el .TP "\\$1" +.. +.TH SETUP 8 "21 May 1994" "Slackware Version 2.0.0" +.SH NAME +setup \- Slackware system setup tool. +.SH SYNOPSIS +.B setup +.LP +.SH DESCRIPTION +.B setup +is the system installation and setup tool provided with the Slackware Linux +distribution. +.LP +.B setup +is usually used to install software packages from your hard drive, a CD, +NFS, or floppy disks. It is also a frontend for +.B pkgtool +and many configuration scripts that come with various packages, such as the +scripts which allow you to install LILO, configure your timezone, set your +keyboard fonts, make bootdisks, and many other tasks. +.SH OPTIONS +.TP +.B HELP +Read the +.B setup +help file. +.TP +.B KEYMAP +Change your keyboard map to one of many international and specialized keymaps +available. +.B NOTE: +This change will not become permanent unless you go through the +.B CONFIGURE option. +.TP +.B MAKE TAGS +This allows you to write out custom tagfiles. A +.B tagfile +is a list of package names followed by one of these tags: +.B ADD +(required), +.B SKP +(skip), +.B REC +(recommended) or, +.B OPT +(optional). These allow you to completely automate your software installation. +You can either put these files on the first disk of each disk series +(optionally using a custom 3 character extension), or in a custom location +altogether, such as on a floppy disk in ./a1, ./ap1, ./d1, ..., directories. +The format of a line in a +.B tagfile +is like this: +.LP +package: +.B TAG +.TP +.B SOURCE +Select your source media, such as hard disk, NFS, CD, or floppy. You should +select installation from a directory if your CD or NFS directory has already +been mounted, as it probably is if you're using +.B setup +on your hard drive. +.TP +.B TARGET +Select your target directory. For testing purposes, you may install the +packages to a directory other than '/'. Don't expect them to run from there, +though. +.TP +.B DISK SETS +Select the disk sets you want to install. You can also install custom disk +sets by tagging the +.B CUS +selection. The disk sets must be Slackware-like: they require the diskxxx? +index on each disk, such as diskxyz1 for the first disk of the XYZ series. +On the last disk there must be a file called +.B install.end +to signal the end of the disk series. +.TP +.B INSTALL +Once you've gone through +.B SOURCE +and +.B DISK SETS +( and possibly +.B TARGET +), then you select this choice to go on with the software installation. You'll +be asked what type of tagfiles you want to use and then +.B pkgtool +will be called to install the software. +.TP +.B CONFIGURE +This option runs through several scripts that configure various aspects of your +Linux system. These might include LILO installation, timezone configuration, +and other things. +.TP +.B PKGTOOL +This option calls the +.B pkgtool(8) +utility for you. +.TP +.B EXIT +Exit the +.B setup +program. +.SH AUTHOR +Patrick J. Volkerding <volkerdi@slackware.com> +.SH "SEE ALSO" +.BR makepkg(8), +.BR installpkg(8), +.BR explodepkg(8), +.BR removepkg(8), +.BR pkgtool(8), +.BR upgradepkg(8) diff --git a/source/a/pkgtools/manpages/upgradepkg.8 b/source/a/pkgtools/manpages/upgradepkg.8 new file mode 100644 index 000000000..8ca7811ba --- /dev/null +++ b/source/a/pkgtools/manpages/upgradepkg.8 @@ -0,0 +1,98 @@ +.\" -*- nroff -*- +.ds g \" empty +.ds G \" empty +.\" Like TP, but if specified indent is more than half +.\" the current line-length - indent, use the default indent. +.de Tp +.ie \\n(.$=0:((0\\$1)*2u>(\\n(.lu-\\n(.iu)) .TP +.el .TP "\\$1" +.. +.TH UPGRADEPKG 8 "31 May 2002" "Slackware Version 8.1.0" +.SH NAME +upgradepkg \- upgrade Slackware packages. +.SH SYNOPSIS +.B upgradepkg +[ +.B --dry-run +] +[ +.B --install-new +] +[ +.B --reinstall +] +[ +.B --verbose +] +.BI newpackagename +.BI [ newpackagename2 ] +.LP +.B upgradepkg +[ +.B --dry-run +] +[ +.B --install-new +] +[ +.B --reinstall +] +[ +.B --verbose +] +.BI oldpackagename%newpackagename +.BI [ old2%new2 ] +.SH DESCRIPTION +.B upgradepkg +upgrades a Slackware package from an older version to a +newer one. It does this by +.B INSTALLING +the new package onto the system, and then +.B REMOVING +any files from the old package that aren't in the new package. +If the old and new packages have the same name, a single argument is all that +is required. If the packages have different names, supply the name of the +old package followed by a percent symbol (%), then the name of the new package. +Do not add any extra whitespace between pairs of old/new package names. + +If upgradepkg finds more than one installed package matching the old package's +name, it will remove them all. +.TP +To upgrade in a directory other than / (such as /mnt): +.TP +ROOT=/mnt upgradepkg package.tgz (or .tbz, .tlz, .txz) +.SH OPTIONS +.TP +.B \--dry-run +Output a report about which packages would be installed or upgraded +but don't actually perform the upgrades. +.TP +.B \--install-new +Normally upgradepkg only upgrades packages that are already installed on the system, and +will skip any packages that do not already have a version installed. +If +.B --install-new +is specified, the behavior is modified to install new packages in addition to upgrading +existing ones. +.TP +.B \--reinstall +Upgradepkg usually skips packages if the exact same package +(matching name, version, arch, and build number) is already installed on the system. +Use the --reinstall option if you want to upgrade all packages even if the same +version is already installed. +.TP +.B \--verbose +Show all the gory details of the upgrade. +.SH BUGS +Before upgrading a package, save any configuration files (such as in /etc) +that you wish to keep. Sometimes these will be preserved, but it depends on +the package structure. If you want to force new versions of the config files +to be installed, remove the old ones manually prior to running upgradepkg. +.SH AUTHOR +Patrick J. Volkerding <volkerdi@slackware.com> +.SH "SEE ALSO" +.BR makepkg(8), +.BR installpkg(8), +.BR removepkg(8), +.BR explodepkg(8), +.BR pkgtool(8) |