Where is make.conf.example

Unless you are doing development work, do not enable ccache. A QA -feature to ensure that a package does not overwrite files it does not own. Also see the related protect-owned feature. The causes all build logs to be compressed while they are being written. Log file names have an extension that is appropriate for the compression type. Currently, only gzip 1 compression is supported, so build logs will have a. Autogenerate digests for packages when running the emerge 1 , ebuild 1 , or repoman 1 commands.

Portage uses lockfiles to ensure competing instances do not clobber each other's files. This feature is enabled by default but may cause heartache on less intelligent remote filesystems like NFSv2 and some strangely configured Samba server oplocks off , NFS re-export. Enable fakeroot for the install and package phases when a non-root user runs the ebuild 1 command. Clean up temporary files after a build failure. Both the ebuild 1 command and the noclean feature cause the fail-clean feature to be automatically disabled.

Runs the script that will fix the dependencies in all binary packages. This is run whenever packages are moved around in the portage tree. Please note that this can take a lot of time.

See make. This feature works only if debugedit is installed and CFLAGS is set to include debug information such as with the -ggdb flag. Due to lack of proper cleanup, this feature can interfere with normal emerge operation and therefore it should not be left enabled for more than a short period of time. Automatically perform a metadata transfer when 'emerge --sync' is run. To find the bad packages, we have a portage feature called multilib-strict.

Enable GLEP 42 news support. Fetch in the background while compiling. Parse EAPI from the head of the ebuild first 30 lines. This feature is only intended for experimental purposes and should not be enabled under normal circumstances.

If prelink 8 is installed then use it to undo any prelinks on files before computing checksums for merge and unmerge. This feature is useful only if prelink 8 is installed and accurate checksums despite prelinking are needed for some reason such as for checking the integrity of installed files or because the unmerge-orphans feature is disabled.

Preserve libraries when the sonames change during upgrade or downgrade. Libraries are preserved only if consumers of those libraries are detected. This is identical to the collision-protect feature except that files may be overwritten if they are not explicitly listed in the contents of a currently installed package. This is particularly useful on systems that have lots of orphan files that have been left behind by older versions of portage that did not support the unmerge-orphans feature.

It is recommended to leave either protect-owned or collision-protect enabled at all times, since otherwise file collisions between packages may result in files being overwritten or uninstalled at inappropriate times.

If collision-protect is enabled then it takes precedence over protect-owned. Output a verbose trace of python execution to stderr when a command's --debug option is enabled. Enable SELinux sandbox -ing. Stands for Smart Filesystem Permissions. Before merging packages to the live filesystem, automatically search for and set permissions on setuid and setgid files. Files that are setuid have the group and other read bits removed while files that are setgid have the other read bit removed.

See also suidctl below. When commiting work to cvs with repoman 1 , sign the Manifest with a GPG key. Prior to stripping ELF etdyn and etexec files, the debugging info is stored for later use by various debuggers. This feature is disabled by nostrip. For installation of source code, see installsources.

Have portage react strongly to conditions that have the potential to be dangerous like missing or incorrect digests for ebuilds. Have portage react strongly to conditions that may conflict with system security provisions for example textrels , executable stack.

In addition, control variables can be specified for a particular build via the -D option of make 1 or in environ 7. In the case of world and kernel builds it is possible to put these variables into src. This way the environment for documentation and ports builds is not pol- luted by unrelated variables. The following lists provide a name and short description for each vari- able you can use during the indicated builds.

The values of variables flagged as bool are ignored; the variable being set at all even to "FALSE" or "NO" causes it to be treated as if it were set. The following list provides a name and short description for variables that are used for all builds, or are used by the makefiles for things other than builds.

Normally this is only done for the world and build- world targets to handle upgrades from older versions of FreeBSD. Optimization levels other than -O and -O2 are not sup- ported. Note that you can set SVN to the full path of a svn 1 binary.

The value is approximately milliseconds. Keypresses are ac- cepted by the BIOS before booting from disk, making it pos- sible to give custom boot parameters even when this is set to 0.

Common choices include nouveau , nvidia , radeon , and intel. For the average user, if a graphical desktop environment is to be used this variable should be explicitly defined. This page contains changes which are not marked for translation. Other languages:.

Note Different configurations will require different variables to be set up. Do not treat the following examples as a definitive list, or a minimum set of requirements. Category : Portage. Starting with portage 2. This variable only makes sense on a system that will serve as a binhost and build packages for clients. This variable contains options to be passed to the tar command for creation of binary packages.

This variable should contain a command that is suitable for portage to call for bunzip2 extraction operations. This variable should contain a command that is suitable for portage to call for bzip2 compression operations. This variable contains the command used to compress documentation during the install phase. Regular expressions are supported and the match is performed only against the portion of the file name which follows the last period character.

Number of mirrors to try when a downloaded file has an incorrect checksum. This is useful for helping to ensure that small garbage files such as html pages are properly discarded.

The variable should contain an integer number of bytes and may have a suffix such as K, M, or G. This variable should contain a command for portage to call in order to adjust the io priority of portage and it's subprocesses.

For more information about ionice, see ionice 1. The value of this variable will be added to the current nice level that emerge is running at. In other words, this will not set the nice level, it will increment it. For more information about nice levels and what are acceptable ranges, see nice 1. Search order is from left to right. Used by emerge --sync as a timeout for the initial connection to an rsync server. Defaults to 15 seconds. Additional rsync options to be used by emerge --sync.

Defaults to no value. Default rsync options to be used by emerge --sync. Don't change this unless you know exactly what you're doing! The number of times rsync should retry on failed connections before giving up. If set to a negative number, then retry until all possible addresses are exhausted. Defaults to A value of 0 will disable warnings. Defines the location of the temporary build directories.

Defines the location of the Portage tree. This is the repository for all profile information as well as all ebuilds. This is a space delimited list of directories. See also ebuild 5. This variable contains the command used for resuming package sources that have been partially downloaded. Use ROOT to specify the target root filesystem to be used for merging packages or ebuilds.

It's commonly used for creating new build images. Make sure you use an absolute path. Defines the location where created RPM packages will be stored. Insert your preferred rsync mirror here. This variable contains options that control the build behavior of several packages. More information in ebuild 5. Determines the precedence of layers in the incremental stacking of the USE variable.

Precedence decreases from left to right such that env overrides pkg, pkg overrides conf, and so forth. If you change this and something breaks, we will not help you fix it. USE from make. Contains variables for the build-process and overwrites those in make.

Development News Calculate Linux. OpenID Server Pastebin.