head	1.4;
access;
symbols
	rpm-3_0_2:1.3
	rpm-3_0:1.3.0.10
	r2-94:1.3
	r2-93:1.3
	r2-92:1.3
	r2-91:1.3
	r2-5-7:1.3
	r2-5-6:1.3
	jbj-pre-automake:1.3
	r2-5-5:1.3
	r2-5-4:1.3
	r2-5-3:1.3
	r2-90:1.3
	branch-r2-5:1.3.0.8
	r2-5-2:1.3
	r2-5-1:1.3
	r2-5:1.3
	r2-4-109:1.3
	r2-4-108:1.3
	r2-4-107:1.3
	r2-4-106:1.3
	r2-4-104:1.3
	r2-4-103:1.3
	r2-4-102:1.3
	r2-4-101:1.3
	r2-4-100:1.3
	r2-4-99:1.3
	r2-4-tree:1.3.0.6
	r-2-4-tree:1.3.0.4
	r2-4-12:1.3
	r2-3-12:1.3
	r2-3-11-patches:1.3.0.2
	r2-4-11:1.3
	r2-4-10:1.3
	r2-4-9:1.3
	r2-4-8:1.3
	r2-4-7:1.3
	r2-4-6:1.3
	r2-4-5:1.3
	r2-4-4:1.3
	r2-4-3:1.3
	r2-4-2:1.3
	r2-4-1:1.3
	r2-3-11:1.3
	r2-4:1.3
	2-3-11:1.3
	2-3-10:1.3
	2-3-9:1.3
	2-3-8:1.3
	2-3-7:1.3
	2-3-6:1.3
	2-3-5:1.3
	2-3-4:1.3
	2-3-3:1.3
	2-3-2:1.3
	2-3-1:1.3
	2-2-11:1.3
	2-2-10:1.3
	2-3:1.3
	2-2-9:1.3
	2-2-8:1.3
	2-2-7:1.3;
locks; strict;
comment	@# @;


1.4
date	99.07.19.22.13.12;	author jbj;	state dead;
branches;
next	1.3;

1.3
date	96.07.16.18.38.21;	author ewt;	state Exp;
branches;
next	1.2;

1.2
date	96.07.14.16.14.01;	author root;	state Exp;
branches;
next	1.1;

1.1
date	96.07.14.16.12.18;	author root;	state Exp;
branches;
next	;


desc
@@


1.4
log
@add pl translation and man pages (Tomasz K?oczko et al).
@
text
@BUILD ROOT
==========

The build root is very similar to Root: (which will be deprecated
soon).  By using Buildroot: in your spec file you are indicating
that your package can be built (installed into and packaged from)
a user-definable directory.  This helps package building by normal
users.

The Spec File
-------------

Simply use

  Buildroot: <dir>

in your spec file.  The acutal buildroot used by RPM during the
build will be available to you (and your %prep, %build, and %install
sections) as the environment variable RPM_BUILD_ROOT.  You must
make sure that the files for the package are installed into the
proper buildroot.  As with Root:, the files listed in the %files
section should *not* contain the buildroot.  For example, the
following hypothetical spec file:

  Name: foo
  ...
  Root: /tmp
  
  %prep
  ...
  
  %build
  ...
  
  %install
  install -m755 fooprog /tmp/usr/bin/fooprog
  
  %files
  /usr/bin/fooprog

would be changed to:

  Name: foo
  ...
  Buildroot: /tmp
  
  %prep
  ...
  
  %build
  ...
  
  %install
  install -m755 fooprog $RPM_BUILD_ROOT/usr/bin/fooprog
  
  %files
  /usr/bin/fooprog

Building With a Build Root
--------------------------

RPM will use the buildroot listed in the spec file as the default
buildroot.  There are two ways to override this.  First, you can
have "buildroot: <dir>" in your rpmrc.  Second, you can override
the default, and any entry in an rpmrc by using "--buildroot <dir>"
on the RPM command line.
@


1.3
log
@*** empty log message ***
@
text
@@


1.2
log
@change "build prefix" to "build root"
@
text
@d4 1
a4 1
The build root is very similar to Root: (which will be depricated
@


1.1
log
@Initial revision
@
text
@d1 2
a2 2
BUILD PREFIX
============
d4 2
a5 2
The build prefix is very similar to Root: (which will be depricated
soon).  By using Buildprefix: in your spec file you are indicating
d15 1
a15 1
  Buildprefix: <dir>
d17 1
a17 1
in your spec file.  The acutal buildprefix used by RPM during the
d19 1
a19 1
sections) as the environment variable RPM_BUILDPREFIX.  You must
d21 2
a22 2
proper buildprefix.  As with Root:, the files listed in the %files
section should *not* contain the buildprefix.  For example, the
d45 1
a45 1
  Buildprefix: /tmp
d54 1
a54 1
  install -m755 fooprog $RPM_BUILDPREFIX/usr/bin/fooprog
d59 2
a60 2
Building With a Build Prefix
----------------------------
d62 4
a65 4
RPM will use the buildprefix listed in the spec file as the default
buildprefix.  There are two ways to override this.  First, you can
have "buildprefix: <dir>" in your rpmrc.  Second, you can override
the default, and any entry in an rpmrc by using "--buildprefix <dir>"
@
