ltsp-build-client(8) [debian man page]

ltsp-build-client(8)													      ltsp-build-client(8)

NAME

       ltsp-build-client - Builds an LTSP client system for use with the LTSP server

SYNOPSIS

       ltsp-build-client  <options>

DESCRIPTION

       ltsp-build-client builds an ltsp client chroot using standard packages for use with the ltsp server.  This chroot installation  can be mod-
       ified in a number of ways as  outlined  in  the	OPTIONS  section.   If	present,  defaults  will  be  read  from  the  configuration  file
       /etc/ltsp/ltsp-build-client.conf,  and  will  be overridden by using the command line options. ltsp-build-client is usually run as the root
       user.  Visit http://www.ltsp.org for more information.

OPTIONS

       Not all options are available on all installations. For a complete list of available options, use the --help and --extra-help options.

       --arch arch
		 Builds a chroot with the specified architecture. Must be a supported architecture of the distribution, and  compatible  with  the
		 host architecture.  Defaults vary by distribution.

       --base dir
		 Sets the default path for the ltsp chroots to be installed into. Defaults to /opt/ltsp/.

       --chroot file
		 Sets the default name for the ltsp chroot. Defaults to the architecture selected with --arch or the running architecture.

       --config file
		 Load configuration defaults from specified file. See CONFIG FILE below for more information.

       --exclude packages
		 Sets packages to exclude from the initial client chroot.

       --extra-help
		 Displays all available commandline options.

       --help	 Displays the ltsp-build-client help message.

       --mirror mirror_url
		 Select the mirror to download packages from. file:/// and http:// URLs are supported.

       --purge-chroot
		 Purges the existing LTSP chroot if present.

CONFIG FILE

       ltsp-build-client  will	read  a  configuration	file  to  override  built-in defaults. the default location for this configuration file is
       /etc/ltsp/ltsp-build-client.conf, and can be specified with the --conf commandline option.

       values are NAME="VALUE" pairs, with # representing commented lines. most commandline options have an equivalent. an  example  Debian  based
       system with an alternate base location, architecture, and distribution:

	# set alternate default location for ltsp chroot (--base)
	BASE="/srv/ltsp"
	# build an amd64 chroot by default (--arch)
	ARCH="amd64"
	# build a Debian sid environment (--dist)
	DIST="sid"

SEE ALSO

       ltsp-update-sshkeys(8), ltsp-update-kernels(8).

AVAILABILITY

       ltsp-build-client is part of ltsp package and the latest versions are available in source form from https://launchpad.net/products/ltsp.

MAN PAGE AUTHOR

       Peter Savage - silentk - cbx33 debug@silentkeystroke.co.uk

       updated 2006, 2009 by Vagrant Cascadian <vagrant@freegeek.org>, 2011 by Wim Muskee <wimmuskee@gmail.com>

								    2011-08-11						      ltsp-build-client(8)

build(1)						      General Commands Manual							  build(1)

NAME

       build - build SuSE Linux RPMs in a chroot environment

SYNOPSIS

       build [--clean|--no-init] [--rpms path1:path2:...]  [--arch arch1:arch2:...]  [--root buildroot] [specfile|srcrpm]
       build --help
       build --verify

DESCRIPTION

       build is a tool to build SuSE Linux RPMs in a safe and clean way.  build will install a minimal SuSE Linux as build system into some direc-
       tory and will chroot to this system to compile the package.  This way you don't risk to corrupt your working system (due to a  broken  spec
       file for example), even if the package does not use BuildRoot.

       build  searches the spec file for a BuildRequires: line; if such a line is found, all the specified rpms are installed.	Otherwise a selec-
       tion of default packages are used. Note that build doesn't automatically resolve missing dependencies, so the specified	rpms  have  to	be
       sufficient for the build.

       If a spec file is specified on the command line, build will use this file and all other files in the directory for building the package. If
       a srcrpm is specified, build automatically unpacks it for the build.  If neither is given, build will use all the specfiles in the  current
       directory.

OPTIONS

       --clean
	      remove the build system and reinitialize it from scratch.

       --no-init
	      skip the build system initialization and start with build immediately.

       --list-state
	      list rpms that would be used to create a fresh build root.  Does not create the build root or perform a build.

       --rpms path1:path2:path3...
	      Where  build  can find the SuSE Linux RPMs needed to create the build system. This option overrides the BUILD_RPMS environment vari-
	      able.

       --arch arch1:arch2:arch3...
	      What architectures to select from the RPMs.  build automatically sets this to a sensible value for your host if  you  don't  specify
	      this option.

       --root buildroot
	      Specifies where the build system is set up. Overrides the BUILD_ROOT enviroment variable.

       --useusedforbuild
	      Tell  build  not	to do dependency expansion, but to extract the list of packages to install from "# usedforbuild" lines or, if none
	      are found, from all "BuildRequires" lines.  This option is useful if you want to re-build a package from a srcrpm with  exactly  the
	      same packages used for the srcrpm build.

       --norootforbuild

       --help Print a short help text.

       --verify
	      verify the files in an existing build system.

.spec FILE OPTIONS
       The build command interprets some special control comments in the specfile:

       # norootforbuild
       # needsrootforbuild
	      build  uses  either  user root or user abuild in the build system to do the build.  For non-SUSE distros as well as since SUSE 10.2,
	      the default build user is abuild.  For 10.2 and before, the default build user is root.  These two flags in the spec file  allow	to
	      deviate  from  the  defaults  and  force-set the build user to abuild and root (for # norootforbuild and # needsrootforbuild respec-
	      tively.

       # needsbinariesforbuild
	      provide the binary rpms that have been used to set up the build root in /.build.binaries within the build root.

ENVIRONMENT

       BUILD_ROOT
	      The directory where build should install the chrooted build system.  "/var/tmp/build-root" is used by default.

       BUILD_RPMS
	      Where build can find the SuSE Linux RPMs.  build needs them to create the build system.	"/media/dvd/suse"  is  the  default  value
	      which will do the trick if you have the SuSE Linux DVD mounted.

       BUILD_RPM_BUILD_STAGE
	      The  rpm	build  stage  (-ba, -bb, ...).	This is just passed through to rpm, check the rpm manpage for a complete list and descrip-
	      tions.  "-ba" is the default.  You can use this to add more options to RPM.

SEE ALSO

       rpm(1),

       Maximum RPM:
	      http://www.rpm.org/max-rpm/

       cross distribution packaging:
	      http://en.opensuse.org/Build_Service/cross_distribution_package_how_to

       SUSE packaging standards and guidelines:
	      http://en.opensuse.org/Packaging

						  (c) 1997-2008 SuSE Linux AG Nuernberg, Germany					  build(1)