1
# Copyright 1999-2019 Gentoo Authors
2
# Distributed under the terms of the GNU General Public License v2
3
# Contains local system settings for Portage system
5
# Please review 'man make.conf' for more information.
7
# Build-time functionality
8
# ========================
10
# The USE variable is used to enable optional build-time functionality. For
11
# example, quite a few packages have optional X, gtk or GNOME functionality
12
# that can only be enabled or disabled at compile-time. Gentoo Linux has a
13
# very extensive set of USE variables described in our USE variable HOWTO at
14
# https://wiki.gentoo.org/wiki/Handbook:X86/Working/USE
16
# The available list of use flags with descriptions is in the ebuild repository.
17
# Use 'less' to view them: --> less /var/db/repos/gentoo/profiles/use.desc <--
19
# 'ufed' is an ncurses/dialog interface available in portage to make handling
20
# useflags for you. 'emerge app-portage/ufed'
23
#USE="X gtk gnome -alsa"
25
# Host and optimization settings
26
# ==============================
28
# For optimal performance, enable a CFLAGS setting appropriate for your CPU.
30
# Please note that if you experience strange issues with a package, it may be
31
# due to gcc's optimizations interacting in a strange way. Please test the
32
# package (and in some cases the libraries it uses) at default optimizations
33
# before reporting errors to developers.
35
# If your gcc supports it, you can add -frecord-gcc-switches to all of the
36
# following *FLAGS in order to enable *FLAGS ignorance checking for ebuilds:
37
# CFLAGS, CXXFLAGS, FFLAGS, and FCFLAGS.
38
# Note that this check is only enabled if every one of these variables contains
39
# -frecord-gcc-switches, since otherwise the check could result in false
42
# Please refer to the GCC manual for a list of possible values.
46
# If you set a CFLAGS above, then this line will set your default C++ flags to
50
# If you set a CFLAGS above, then this line will set your default FORTRAN 77
51
# flags to the same settings.
54
# If you set a FFLAGS above, then this line will set your default FORTRAN
55
# flags to the same settings for modern build systems
62
# Gentoo is using a new masking system to allow for easier stability testing
63
# on packages. KEYWORDS are used in ebuilds to mask and unmask packages based
64
# on the platform they are set for. A special form has been added that
65
# indicates packages and revisions that are expected to work, but have not yet
66
# been approved for the stable set. '~arch' is a superset of 'arch' which
67
# includes the unstable, in testing, packages. Users of the 'x86' architecture
68
# would add '~x86' to ACCEPT_KEYWORDS to enable unstable/testing packages.
69
# '~ppc', '~sparc' are the unstable KEYWORDS for their respective platforms.
71
# Please note that this is not for development, alpha, beta, nor cvs release
72
# packages. "Broken" packages will not be added to testing and should not be
73
# requested to be added. Alternative routes are available to developers
74
# for experimental packages, and it is at their discretion to use them.
76
# DO NOT PUT ANYTHING BUT YOUR SPECIFIC ~ARCHITECTURE IN THE LIST.
77
# IF YOU ARE UNSURE OF YOUR ARCH, OR THE IMPLICATIONS, DO NOT MODIFY THIS.
79
#ACCEPT_KEYWORDS="~arch"
81
# ACCEPT_LICENSE is used to mask packages based on licensing restrictions.
82
# It may contain both license and group names, where group names are
83
# prefixed with the '@' symbol. License groups are defined in the
84
# license_groups file (see portage(5) man page). In addition to license
85
# and group names, the * and -* wildcard tokens are also supported.
87
# Only accept licenses in the FREE license group (i.e. Free Software).
88
#ACCEPT_LICENSE="-* @FREE"
90
# Accept any license except those in the EULA license group.
91
#ACCEPT_LICENSE="* -@EULA"
96
# Each of these settings controls an aspect of portage's storage and file
97
# system usage. If you change any of these, be sure it is available when
98
# you try to use portage. *** DO NOT INCLUDE A TRAILING "/" ***
100
# PORTAGE_TMPDIR is the location portage will use for compilations and
101
# temporary storage of data. This can get VERY large depending upon
102
# the application being installed.
103
#PORTAGE_TMPDIR=/var/tmp
105
# PORTDIR is the location of the ebuild repository. This is the repository
106
# for all profile information as well as all ebuilds. If you change
107
# this, you must update your /etc/portage/make.profile symlink accordingly.
109
# Data stored inside PORTDIR is in peril of being overwritten or deleted by
110
# the emerge --sync command.
111
#PORTDIR=/var/db/repos/gentoo
113
# DISTDIR is where all of the source code tarballs will be placed for
114
# emerges. After packages are built, it is safe to remove any and
115
# all files from this directory since they will be automatically
116
# fetched on demand for a given build. If you would like to
117
# selectively prune obsolete files from this directory, see
118
# eclean from the gentoolkit package.
119
#DISTDIR=/var/cache/distfiles
121
# PKGDIR is the location of binary packages that you can have created
122
# with '--buildpkg' or '-b' while emerging a package. This can get
123
# up to several hundred megs, or even a few gigs.
124
#PKGDIR=/var/cache/binpkgs
126
# PORTAGE_LOGDIR is the location where portage will store all the logs it
127
# creates from each individual merge. They are stored as
128
# ${CATEGORY}:${PF}:YYYYMMDD-HHMMSS.log in the directory specified.129
# If the directory does not exist, it will be created automatically and
130
# group permissions will be applied to it. If the directory already
131
# exists, portage will not modify its permissions.
134
# PORTDIR_OVERLAY is a directory where local ebuilds may be stored without
135
# concern that they will be deleted by rsync updates. Default is not
137
#PORTDIR_OVERLAY=/usr/local/portage
142
# If you need to set a proxy for wget or lukemftp, add the appropriate "export
143
# ftp_proxy=<proxy>" and "export http_proxy=<proxy>" lines to /etc/profile if
144
# all users on your system should use them.
146
# Portage uses wget by default. Here are some settings for some alternate
147
# downloaders -- note that you need to merge these programs first before they
148
# will be available. The command should be written to place the fetched file
149
# at \${DISTDIR}/\${FILE}.151
# Default fetch command (3 tries, passive ftp for firewall compatibility)
152
#FETCHCOMMAND="wget -t 3 -T 60 --passive-ftp -O \"\${DISTDIR}/\${FILE}\" \"\${URI}\""153
#RESUMECOMMAND="wget -c -t 3 -T 60 --passive-ftp -O \"\${DISTDIR}/\${FILE}\" \"\${URI}\""155
# Using wget, ratelimiting downloads
156
#FETCHCOMMAND="wget -t 3 -T 60 --passive-ftp --limit-rate=200k -O \"\${DISTDIR}/\${FILE}\" \"\${URI}\""157
#RESUMECOMMAND="wget -c -t 3 -T 60 --passive-ftp --limit-rate=200k -O \"\${DISTDIR}/\${FILE}\" \"\${URI}\""160
#FETCHCOMMAND="/usr/bin/lukemftp -s -a -o \"\${DISTDIR}/\${FILE}\" \"\${URI}\""161
#RESUMECOMMAND="/usr/bin/lukemftp -s -a -R -o \"\${DISTDIR}/\${FILE}\" \"\${URI}\""163
# Portage uses GENTOO_MIRRORS to specify mirrors to use for source retrieval.
164
# The list is a space separated list which is read left to right. If you use
165
# another mirror we highly recommend leaving the default mirror at the end of
166
# the list so that portage will fall back to it if the files cannot be found
167
# on your specified mirror. We _HIGHLY_ recommend that you change this setting
168
# to a nearby mirror by merging and using the 'mirrorselect' tool.
169
#GENTOO_MIRRORS="<your_mirror_here> http://distfiles.gentoo.org http://www.ibiblio.org/pub/Linux/distributions/gentoo"
171
# Portage uses PORTAGE_BINHOST to specify mirrors for prebuilt-binary packages.
172
# The list is a single entry specifying the full address of the directory
173
# serving the tbz2's for your system. Running emerge with either '--getbinpkg'
174
# or '--getbinpkgonly' will cause portage to retrieve the metadata from all
175
# packages in the directory specified, and use that data to determine what will
176
# be downloaded and merged. '-g' or '-gK' are the recommend parameters. Please
177
# consult the man pages and 'emerge --help' for more information. For FTP, the
178
# default connection is passive -- If you require an active connection, affix
179
# an asterisk (*) to the end of the host:port string before the path.
180
#PORTAGE_BINHOST="http://grp.mirror.site/gentoo/grp/1.4/i686/athlon-xp/"
181
# This ftp connection is passive ftp.
182
#PORTAGE_BINHOST="ftp://login:pass@grp.mirror.site/pub/grp/i686/athlon-xp/"
183
# This ftp connection is active ftp.
184
#PORTAGE_BINHOST="ftp://login:pass@grp.mirror.site:21*/pub/grp/i686/athlon-xp/"
186
# Binary packages GPG commands
187
# ============================
189
# Only works with GPKG format.
190
# "binpkg-signing" needed to be set in FEATURES if need signing packages.
191
# "binpkg-request-signature" needed to be set in FEATURES if you want all
192
# binpkgs must have signature.
193
# You need uncomment related commands and set "USER" and "SIGN_KEY" to yours.
195
# Binary package GPG singing base command
196
# Basic command for all signature operations.
197
# You need change this if you want to use other configurations,
198
# Note that some configurations are configured separately below,
199
# please do not add duplicate configurations
200
#BINPKG_GPG_SIGNING_BASE_COMMAND="/usr/bin/flock /run/lock/portage-binpkg-gpg.lock /usr/bin/gpg --sign --armor [PORTAGE_CONFIG]"
202
# Binary package GPG signature digests algorithm.
203
#BINPKG_GPG_SIGNING_DIGEST="SHA512"
205
# gnupg home directory used for signing.
206
#BINPKG_GPG_SIGNING_GPG_HOME="/root/.gnupg"
208
# GPG key ID used for signing.
209
#BINPKG_GPG_SIGNING_KEY="0x1234567890ABCD!"
211
# Binary package GPG verify base command.
212
# Basic command for all verify operations.
213
#BINPKG_GPG_VERIFY_BASE_COMMAND="/usr/bin/gpg --verify --batch --no-tty --no-auto-check-trustdb --status-fd 2 [PORTAGE_CONFIG] [SIGNATURE]"
215
# GPG home directory where store all trust binary package public keys.
216
#BINPKG_GPG_VERIFY_GPG_HOME="/etc/portage/gnupg"
218
# The user and group will be used when drop root privileges during GPG verify
219
#GPG_VERIFY_USER_DROP="nobody"
220
#GPG_VERIFY_GROUP_DROP="nogroup"
222
# Synchronizing Portage
223
# =====================
225
# Each of these settings affects how Gentoo synchronizes the ebuild repository.
226
# Synchronization is handled by rsync and these settings allow some control
227
# over how it is done.
229
# SYNC is the server used by rsync to retrieve a localized rsync mirror
230
# rotation. This allows you to select servers that are geographically
231
# close to you, yet still distribute the load over a number of servers.
232
# Please do not single out specific rsync mirrors. Doing so places undue
233
# stress on particular mirrors. Instead you may use one of the following
234
# continent specific rotations:
236
# Default: "rsync://rsync.gentoo.org/gentoo-portage"
237
# North America: "rsync://rsync.namerica.gentoo.org/gentoo-portage"
238
# South America: "rsync://rsync.samerica.gentoo.org/gentoo-portage"
239
# Europe: "rsync://rsync.europe.gentoo.org/gentoo-portage"
240
# Asia: "rsync://rsync.asia.gentoo.org/gentoo-portage"
241
# Australia: "rsync://rsync.au.gentoo.org/gentoo-portage"
243
# If you have multiple Gentoo boxes, it is probably a good idea to have only
244
# one of them sync from the rotations above. The other boxes can then rsync
245
# from the local rsync server, reducing the load on the mirrors.
246
# Instructions for setting up a local rsync server are available here:
247
# https://wiki.gentoo.org/wiki/Local_Mirror
249
#SYNC="rsync://rsync.gentoo.org/gentoo-portage"
251
# PORTAGE_RSYNC_RETRIES sets the number of times portage will attempt to retrieve
252
# a current ebuild repository before it exits with an error. This allows
253
# for a more successful retrieval without user intervention most times.
254
# If set to a negative number, then retry until all possible addresses are
256
#PORTAGE_RSYNC_RETRIES="-1"
258
# PORTAGE_RSYNC_EXTRA_OPTS can be used to feed additional options to the rsync
259
# command used by `emerge --sync`. This will not change the default options
260
# which are set by PORTAGE_RSYNC_OPTS (don't change those unless you know
261
# exactly what you're doing).
262
#PORTAGE_RSYNC_EXTRA_OPTS=""
267
# EMERGE_DEFAULT_OPTS allows emerge to act as if certain options are
268
# specified on every run. Useful options include --ask, --verbose,
269
# --usepkg and many others. Options that are not useful, such as --help,
271
#EMERGE_DEFAULT_OPTS=""
273
# INSTALL_MASK allows certain files to not be installed into your file system.
274
# This is useful when you wish to filter out a certain set of files from
275
# ever being installed, such as INSTALL.gz or TODO.gz
278
# MAKEOPTS provides extra options that may be passed to 'make' when a
279
# program is compiled. Presently the only use is for specifying
280
# the number of parallel makes (-j) to perform. The suggested number
281
# for parallel makes is CPUs+1.
284
# PORTAGE_NICENESS provides a default increment to emerge's niceness level.
285
# Note: This is an increment. Running emerge in a niced environment will
286
# reduce it further. Default is unset.
289
# PORTAGE_IONICE_COMMAND provides a command for portage to call in order to
290
# adjust the io priority of portage and its subprocesses. Default is
292
#PORTAGE_IONICE_COMMAND="ionice -c 3 -p \${PID}"294
# PORTAGE_SCHEDULING_POLICY allows changing the current scheduling policy. The
295
# supported options are 'other', 'batch', 'idle', 'fifo', 'round-robin' and
296
# 'deadline'. When unset, the scheduling policy remains unchanged, by default
297
# Linux uses 'other' policy. Users that wish to minimize the Portage's impact
298
# on system responsiveness should set scheduling policy to 'idle' which
299
# significantly reduces the disruption to the rest of the system by scheduling
300
# Portage as extremely low priority processes.
302
#PORTAGE_SCHEDULING_POLICY="idle"
304
# PORTAGE_SCHEDULING_PRIORITY allows changing the priority (1-99) of the current
305
# scheduling policy, only applies if PORTAGE_SCHEDULING_POLICY is set to 'fifo'
306
# or 'round-robin', for others the only supported priority is 0, If unset,
307
# defaults to lowest priority of the selected scheduling policy.
309
#PORTAGE_SCHEDULING_PRIORITY="99"
311
# AUTOCLEAN enables portage to automatically clean out older or overlapping
312
# packages from the system after every successful merge. This is the
313
# same as running 'emerge -c' after every merge. Set with: "yes" or "no".
314
# This does not affect the unpacked source. See 'noclean' below.
316
# Warning: AUTOCLEAN="no" can cause serious problems due to overlapping
317
# packages. Do not use it unless absolutely necessary!
320
# FEATURES defines actions portage takes by default. This is an incremental
321
# variable. See the make.conf(5) man page for a complete list of supported
322
# values and their respective meanings.
323
#FEATURES="ccache distcc installsources \
324
# splitdebug test userpriv usersandbox"
326
# CCACHE_SIZE and CCACHE_DIR are used to control the behavior of ccache, and
327
# and are only used if "ccache" is in FEATURES.
329
# CCACHE_SIZE sets the space limitations for ccache. The default size depends
330
# on ccache itself; see the -M flag in the ccache(1) man page for details.
334
# CCACHE_DIR sets the ccache path. If not specified, portage will default
335
# to "${PORTAGE_TMPDIR}/ccache".337
# Note that to display ccache statistics outside of portage, you must
338
# remember to give the correct path to the cache.
340
# $ CCACHE_DIR=/var/tmp/ccache ccache -s
342
#CCACHE_DIR="${PORTAGE_TMPDIR}/ccache"344
# DISTCC_DIR sets the temporary space used by distcc.
345
#DISTCC_DIR="${PORTAGE_TMPDIR}/.distcc"347
# logging related variables:
348
# PORTAGE_ELOG_CLASSES: selects messages to be logged, possible values are:
349
# info, warn, error, log, qa, *
350
#PORTAGE_ELOG_CLASSES="log warn error"
352
# PORTAGE_ELOG_SYSTEM: selects the module(s) to process the log messages. Modules
353
# included in portage are (empty means logging is disabled):
354
# echo (display messages again when emerge exits)
355
# save (saves one log per package in $PORTAGE_LOGDIR/elog,
356
# /var/log/portage/elog if $PORTAGE_LOGDIR is unset)
357
# custom (passes all messages to $PORTAGE_ELOG_COMMAND)
358
# syslog (sends all messages to syslog)
359
# mail (send all messages to the mailserver defined
360
# in $PORTAGE_ELOG_MAILURI)
361
# save_summary (like "save" but merges all messages
362
# in $PORTAGE_LOGDIR/elog/summary.log,
363
# /var/log/portage/elog/summary.log if
364
# $PORTAGE_LOGDIR is unset)
365
# mail_summary (like "mail" but sends all messages in
366
# a single mail when emerge exits)
367
# To use elog you should enable at least one module
368
# The module name may be followed by a colon and a comma
369
# separated list of loglevels to override PORTAGE_ELOG_CLASSES
370
# for this module (e.g.
371
# PORTAGE_ELOG_SYSTEM="mail:warn,error syslog:* save")
372
#PORTAGE_ELOG_SYSTEM="save_summary:log,warn,error,qa echo"
374
# PORTAGE_ELOG_COMMAND: only used with the "custom" logging module. Specifies a command
375
# to process log messages. Two variables are expanded:
376
# ${PACKAGE} - expands to the cpv entry of the processed377
# package (see $PVR in ebuild(5))
378
# ${LOGFILE} - absolute path to the logfile379
# Both variables have to be quoted with single quotes
380
#PORTAGE_ELOG_COMMAND="/path/to/logprocessor -p '\${PACKAGE}' -f '\${LOGFILE}'"382
# PORTAGE_ELOG_MAILURI: this variable holds all important settings for the mail
383
# module. In most cases listing the recipient address and
384
# the receiving mailserver should be sufficient, but you can
385
# also use advanced settings like authentication or TLS. The
387
# address [[user:passwd@]mailserver[:port]]
389
# address: recipient address
390
# user: username for smtp auth (defaults to none)
391
# passwd: password for smtp auth (defaults to none)
392
# mailserver: smtp server that should be used to deliver the mail (defaults to localhost)
393
# alternatively this can also be a the path to a sendmail binary if you don't want to use smtp
394
# port: port to use on the given smtp server (defaults to 25, values > 100000 indicate that starttls should be used on (port-100000))
396
#PORTAGE_ELOG_MAILURI="root@localhost localhost" (this is also the default setting)
397
#PORTAGE_ELOG_MAILURI="user@some.domain mail.some.domain" (sends mails to user@some.domain using the mailserver mail.some.domain)
398
#PORTAGE_ELOG_MAILURI="user@some.domain user:secret@mail.some.domain:100465" (this is left uncommented as a reader exercise ;)
400
# PORTAGE_ELOG_MAILFROM: you can set the from-address of logmails with this variable,
401
# if unset mails are sent by "portage" (this default may fail
402
# in some environments).
403
#PORTAGE_ELOG_MAILFROM="portage@some.domain"
405
# PORTAGE_ELOG_MAILSUBJECT: template string to be used as subject for logmails. The following
406
# variables are expanded:
407
# ${ACTION} - merged, unmerged, or unknown408
# ${PACKAGE} - see description of PORTAGE_ELOG_COMMAND409
# ${HOST} - FQDN of the host portage is running on410
#PORTAGE_ELOG_MAILSUBJECT="[portage] ebuild log for \${PACKAGE} on \${HOST}"