Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

pkgenpack(1) [debian 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. --update 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 /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

GO-BUILD(1)						      General Commands Manual						       GO-BUILD(1)

NAME
go - tool for managing Go source code SYNOPSIS
go build [-o output] [ build flags ] [ packages ] DESCRIPTION
Build compiles the packages named by the import paths, along with their dependencies, but it does not install the results. If the arguments are a list of .go files, build treats them as a list of source files specifying a single package. When the command line specifies a single main package, build writes the resulting executable to output. Otherwise build compiles the pack- ages but discards the results, serving only as a check that the packages can be built. The -o flag specifies the output file name. If not specified, the name is packagename.a (for a non-main package) or the base name of the first source file (for a main package). OPTIONS
The build flags are shared by the build, install, run, and test commands: -a force rebuilding of packages that are already up-to-date. -n print the commands but do not run them. -p n the number of builds that can be run in parallel. The default is the number of CPUs available. -v print the names of packages as they are compiled. -work print the name of the temporary work directory and do not delete it when exiting. -x print the commands. -compiler name name of compiler to use, as in runtime.Compiler (gccgo or gc) -gccgoflags 'arg list' arguments to pass on each gccgo compiler/linker invocation -gcflags 'arg list' arguments to pass on each 5g, 6g, or 8g compiler invocation -ldflags 'flag list' arguments to pass on each 5l, 6l, or 8l linker invocation -tags 'tag list' a list of build tags to consider satisfied during the build. See the documentation for the go/build package for more information about build tags. For more about specifying packages, see go-packages(7). For more about where packages and binaries are installed, see go-gopath(1). SEE ALSO
go-install(1), go-get(1), go-clean(1). AUTHOR
This manual page was written by Michael Stapelberg <stapelberg@debian.org>, for the Debian project (and may be used by others). 2012-05-13 GO-BUILD(1)
Man Page