Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

pkgenpack(1) [centos man page]

PKGENPACK(1)							  [FIXME: manual]						      PKGENPACK(1)

NAME
pkgenpack - PackageKit Pack Generator SYNOPSIS
pkgenpack [--help] [--verbose] [--with-package-list] [--output] [--package] [--updates] DESCRIPTION
This manual page documents briefly the pkgenpack command. pkgenpack is the command line client for PackageKit for creating service packs. WHAT IS A SERVICE PACK
? A service pack is a tarball which contains a set of packages and their dependencies. The user can reduce the dependencies to be packed using the --with-package-list option. Along with the dependencies, a service pack has a file named metadata.conf which contains the information about the distribution and creation date of the pack. CREATING A SERVICE PACK
? A service pack is created using the command pkgenpack. OPTIONS
This program follows the usual GNU command line syntax, with long options starting with two dashes (`-'). A summary of options is included below. --help Show summary of options. --verbose Show extra debugging information. --with-package-list Set the filename of dependencies to be excluded. Generally, the file list of packages is generated when doing a PackageKit refresh on the target system. If not specified, pkgenpack uses /var/lib/PackageKit/system.package-list by default. --output The directory to put the pack file, or the current directory if omitted. --package The package to be put into the ServicePack. --updates Put all updates available in the ServicePack. NAMING A SERVICE PACK
The only valid extension for a service pack is ".servicepack". EXAMPLES
1. Tim is facing problems with his Internet connection at home. He needs a service pack with valgrind and it's dependencies for his system. He asks James to generate a pack for him. Both know James's system should contain similar packages as Tim's system, as both of them have installed Fedora 9 two days ago. James simply runs: [james@jamesbook:~]$ pkgenpack --output=/media/USB/TimPacks --package=valgrind This generates a file /media/USB/TimPacks/valgrind-fedora-9-i686.servicepack on the USB key Tim gave to James. Tim can now go home, insert the USB key and double clicks on the valgrind-fedora-9-i686.servicepack file to be prompted to install these packages. 2. Bill wants to create a service pack named kdegames-fedora-9-i686.servicepack for his new system which does not have an internet connection. He generates a list of packages on his system using pkcon list-create and copies that list to his USB key. He then gives that USB to Rishi who has a good internet connectivity. Rishi runs the following command on his system: [rishi@devils-temple:~]$ pkgenpack --with-package-list=/media/USB/bill.package-list --output=/home/rishi/Desktop --program=kdegames This generates a service pack, kdegames-fedora-9-i686.servicepack, on Rishi's Desktop, which can be distributed to Bill and users with similar requirements. INSTALLING A SERVICE PACK
Service Packs can be installed using pkcon. For example: [hacker@tim-lounge:~]$ pkcon install-local /media/USB/TimPacks/valgrind-fedora-9-i686.servicepack SEE ALSO
pkmon (1). pkcon(1). AUTHOR
This manual page was written by Shishir Goel <crazyontheedge@gmail.com> and Richard Hughes <richard@hughsie.com>. COPYRIGHT
Copyright (C) 2008 Shishir Goel [FIXME: source] 31 July,2008 PKGENPACK(1)

Check Out this Related Man Page

GIT-INDEX-PACK(1)						    Git Manual							 GIT-INDEX-PACK(1)

NAME
git-index-pack - Build pack index file for an existing packed archive SYNOPSIS
git index-pack [-v] [-o <index-file>] <pack-file> git index-pack --stdin [--fix-thin] [--keep] [-v] [-o <index-file>] [<pack-file>] DESCRIPTION
Reads a packed archive (.pack) from the specified file, and builds a pack index file (.idx) for it. The packed archive together with the pack index can then be placed in the objects/pack/ directory of a Git repository. OPTIONS
-v Be verbose about what is going on, including progress status. -o <index-file> Write the generated pack index into the specified file. Without this option the name of pack index file is constructed from the name of packed archive file by replacing .pack with .idx (and the program fails if the name of packed archive does not end with .pack). --stdin When this flag is provided, the pack is read from stdin instead and a copy is then written to <pack-file>. If <pack-file> is not specified, the pack is written to objects/pack/ directory of the current Git repository with a default name determined from the pack content. If <pack-file> is not specified consider using --keep to prevent a race condition between this process and git repack. --fix-thin Fix a "thin" pack produced by git pack-objects --thin (see git-pack-objects(1) for details) by adding the excluded objects the deltified objects are based on to the pack. This option only makes sense in conjunction with --stdin. --keep Before moving the index into its final destination create an empty .keep file for the associated pack file. This option is usually necessary with --stdin to prevent a simultaneous git repack process from deleting the newly constructed pack and index before refs can be updated to use objects contained in the pack. --keep=<msg> Like --keep create a .keep file before moving the index into its final destination, but rather than creating an empty file place <msg> followed by an LF into the .keep file. The <msg> message can later be searched for within all .keep files to locate any which have outlived their usefulness. --index-version=<version>[,<offset>] This is intended to be used by the test suite only. It allows to force the version for the generated pack index, and to force 64-bit index entries on objects located above the given offset. --strict Die, if the pack contains broken objects or links. --threads=<n> Specifies the number of threads to spawn when resolving deltas. This requires that index-pack be compiled with pthreads otherwise this option is ignored with a warning. This is meant to reduce packing time on multiprocessor machines. The required amount of memory for the delta search window is however multiplied by the number of threads. Specifying 0 will cause Git to auto-detect the number of CPU's and use maximum 3 threads. NOTE
Once the index has been created, the list of object names is sorted and the SHA-1 hash of that list is printed to stdout. If --stdin was also used then this is prefixed by either "pack ", or "keep " if a new .keep file was successfully created. This is useful to remove a .keep file used as a lock to prevent the race with git repack mentioned above. GIT
Part of the git(1) suite Git 1.8.3.1 06/10/2014 GIT-INDEX-PACK(1)
Man Page