From 9e7a1c8fb4624ae737c9ba9ead8ddfd9a1f15fd7 Mon Sep 17 00:00:00 2001 From: nott Date: Thu, 13 Jun 2013 15:10:50 +0000 Subject: [PATCH] clarify cleantar option git-svn-id: https://svn.code.sf.net/p/xcat/code/xcat-core/trunk@16621 8638fb3e-16cb-4fca-ae20-7b5d299a9bcd --- xCAT-buildkit/pods/man1/buildkit.1.pod | 38 ++++++++++++++++++-------- 1 file changed, 27 insertions(+), 11 deletions(-) diff --git a/xCAT-buildkit/pods/man1/buildkit.1.pod b/xCAT-buildkit/pods/man1/buildkit.1.pod index 63d295a2f..ef68eb923 100644 --- a/xCAT-buildkit/pods/man1/buildkit.1.pod +++ b/xCAT-buildkit/pods/man1/buildkit.1.pod @@ -8,11 +8,11 @@ B [B<-?>|B<-h>|B<--help>] [B<-v>|B<--version>] To build a new Kit -B [B<-V>|B<--verbose]> I [I] [I|B] [B<-l>|B<--kitloc> I] +B [B<-V>|B<--verbose]> I [I] [I|B] [B<-l>|B<--kitloc> I] To add packages to an existing Kit. -B [B<-V>|B<--verbose>] I I [B<-p>|B<--pkgdir> I] [B<-k>|B<--kitversion> I] [B<-r>|B<--kitrelease> I] [B<-l>|B<--kitloc> I] +B [B<-V>|B<--verbose>] I I [B<-p>|B<--pkgdir> I] [B<-k>|B<--kitversion> I] [B<-r>|B<--kitrelease> I] [B<-l>|B<--kitloc> I] =head1 DESCRIPTION @@ -20,9 +20,9 @@ The B command provides a collection of utilities that may be used to p You will need to run the B command several times with different subcommands to step through the process of building a kit: -By default the B subcommands will operate in the current working directory, (ie. look for files, create directories etc.). You could specify a different location by using the "B<-l | --kitloc> I" option. +By default the B subcommands will operate in the current working directory, (ie. look for files, create directories etc.). You could specify a different location by using the "B<-l | --kitloc> I" option. -The kit I is the full path name of the directory that contains the kit files. You would use the same location value for all the buildkit subcommands. +The I is the full path name of the directory that contains the kit files. You would use the same location value for all the buildkit subcommands. For example, to create a new kit named "prodkit" in the directory /home/mykits/ I run: @@ -122,9 +122,9 @@ Display usage message. Product version. -=item B<-l|--kitloc> +=item B<-l|--kitloc> I -The location of the Kit (including the Kit name). +The directory location of the Kit files. =item B<-r|--kitrelease> I @@ -158,19 +158,35 @@ Reads the buildkit.conf file, lists all Kit package repositories listed in the f =item B {I | B} -Reads the buildkit.conf file, and builds the specified Kit package repository. The built packages are placed in the directory /build/kit_repodir/I. If B is specified, all kit repositories are built. +Reads the buildkit.conf file, and builds the specified Kit package repository. The built packages are placed in the directory /build/kit_repodir/I. If B is specified, all kit repositories are built. =item B {I | B} -Reads the buildkit.conf file, and deletes all the package files and package meta data files from the /build/kit_repodir/I directory. If B is specified, all kit repository files are deleted. +Reads the buildkit.conf file, and deletes all the package files and package meta data files from the /build/kit_repodir/I directory. If B is specified, all kit repository files are deleted. =item B -Reads the buildkit.conf file, validates that all kit repositories have been built, and builds the Kit tar file /I.tar.bz2. +Reads the buildkit.conf file, validates that all kit repositories have been built, and builds the Kit tar file /I.tar.bz2. =item B -Reads the buildkit.conf file, deletes the Kit tar /I.tar.bz2, and deletes all files in the build work directory /build/I. +Reads the /buildkit.conf file and I the following: + +=over 4 + +- Kit tar files matching /I. + +- /build/I + +- /rpmbuild + +- /tmp + +- /debbuild + +=back + +Caution: Make sure you back up any tar files you would like to keep before running this subcommand. =item B @@ -180,7 +196,7 @@ Equivalent to running B and B. I {B<-p> | B<--pkgdir> I} [B<-k> | B<--kitversion> I] [B<-r> | B<--kitrelease> I] -Add product package rpms to a previously built kit tar file. This is used for partial product kits that are built and shipped separately from the product packages, and are identified with a I name of I.B. Optionally, change the kit release and version values when building the new kit tarfile. If kitcomponent version and/or release values are defaulted to the kit values, those will also be changed and new kitcomponent rpms will be built. If kit or kitcomponent scripts, plugins, or other files specify name, release, or version substitution strings, these will all be replaced with the new values when built into the new complete kit tarfile I/I.B. +Add product package rpms to a previously built kit tar file. This is used for partial product kits that are built and shipped separately from the product packages, and are identified with a I name of I.B. Optionally, change the kit release and version values when building the new kit tarfile. If kitcomponent version and/or release values are defaulted to the kit values, those will also be changed and new kitcomponent rpms will be built. If kit or kitcomponent scripts, plugins, or other files specify name, release, or version substitution strings, these will all be replaced with the new values when built into the new complete kit tarfile I/I.B. =back