1 # Copyright 1999-2011 Gentoo Foundation
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 # http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=1
16 # The available list of use flags with descriptions is in your portage tree.
17 # Use 'less' to view them: --> less /usr/portage/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 # Please refer to the GCC manual for a list of possible values.
39 # If you set a CFLAGS above, then this line will set your default C++ flags to
43 # If you set a CFLAGS above, then this line will set your default FORTRAN 77
44 # flags to the same settings.
47 # If you set a FFLAGS above, then this line will set your default FORTRAN
48 # flags to the same settings for modern build systems
55 # Gentoo is using a new masking system to allow for easier stability testing
56 # on packages. KEYWORDS are used in ebuilds to mask and unmask packages based
57 # on the platform they are set for. A special form has been added that
58 # indicates packages and revisions that are expected to work, but have not yet
59 # been approved for the stable set. '~arch' is a superset of 'arch' which
60 # includes the unstable, in testing, packages. Users of the 'x86' architecture
61 # would add '~x86' to ACCEPT_KEYWORDS to enable unstable/testing packages.
62 # '~ppc', '~sparc' are the unstable KEYWORDS for their respective platforms.
64 # Please note that this is not for development, alpha, beta, nor cvs release
65 # packages. "Broken" packages will not be added to testing and should not be
66 # requested to be added. Alternative routes are available to developers
67 # for experimental packages, and it is at their discretion to use them.
69 # DO NOT PUT ANYTHING BUT YOUR SPECIFIC ~ARCHITECTURE IN THE LIST.
70 # IF YOU ARE UNSURE OF YOUR ARCH, OR THE IMPLICATIONS, DO NOT MODIFY THIS.
72 #ACCEPT_KEYWORDS="~arch"
77 # Each of these settings controls an aspect of portage's storage and file
78 # system usage. If you change any of these, be sure it is available when
79 # you try to use portage. *** DO NOT INCLUDE A TRAILING "/" ***
81 # PORTAGE_TMPDIR is the location portage will use for compilations and
82 # temporary storage of data. This can get VERY large depending upon
83 # the application being installed.
84 #PORTAGE_TMPDIR=/var/tmp
86 # PORTDIR is the location of the portage tree. This is the repository
87 # for all profile information as well as all ebuilds. If you change
88 # this, you must update your /etc/make.profile symlink accordingly.
90 # Data stored inside PORTDIR is in peril of being overwritten or deleted by
91 # the emerge --sync command. The default value of PORTAGE_RSYNC_OPTS
92 # will protect the default locations of DISTDIR and PKGDIR, but users are
93 # warned that any other locations inside PORTDIR are not necessarily safe
97 # DISTDIR is where all of the source code tarballs will be placed for
98 # emerges. After packages are built, it is safe to remove any and
99 # all files from this directory since they will be automatically
100 # fetched on demand for a given build. If you would like to
101 # selectively prune obsolete files from this directory, see
102 # eclean from the gentoolkit package. Note that locations under
103 # /usr/portage are not necessarily safe for data storage. See the
104 # PORTDIR documentation for more information.
105 #DISTDIR=/usr/portage/distfiles
107 # PKGDIR is the location of binary packages that you can have created
108 # with '--buildpkg' or '-b' while emerging a package. This can get
109 # up to several hundred megs, or even a few gigs. Note that
110 # locations under /usr/portage are not necessarily safe for data
111 # storage. See the PORTDIR documentation for more information.
112 #PKGDIR=/usr/portage/packages
114 # PORT_LOGDIR is the location where portage will store all the logs it
115 # creates from each individual merge. They are stored as
116 # ${CATEGORY}:${PF}:YYYYMMDD-HHMMSS.log in the directory specified.
117 # If the direcory does not exist, it will be created automatically and
118 # group permissions will be applied to it. If the directory already
119 # exists, portage will not modify it's permissions.
122 # PORTDIR_OVERLAY is a directory where local ebuilds may be stored without
123 # concern that they will be deleted by rsync updates. Default is not
125 #PORTDIR_OVERLAY=/usr/local/portage
130 # If you need to set a proxy for wget or lukemftp, add the appropriate "export
131 # ftp_proxy=<proxy>" and "export http_proxy=<proxy>" lines to /etc/profile if
132 # all users on your system should use them.
134 # Portage uses wget by default. Here are some settings for some alternate
135 # downloaders -- note that you need to merge these programs first before they
136 # will be available. The command should be written to place the fetched file
137 # at \${DISTDIR}/\${FILE}.
139 # Default fetch command (3 tries, passive ftp for firewall compatibility)
140 #FETCHCOMMAND="/usr/bin/wget -t 3 -T 60 --passive-ftp -O \"\${DISTDIR}/\${FILE}\" \"\${URI}\""
141 #RESUMECOMMAND="/usr/bin/wget -c -t 3 -T 60 --passive-ftp -O \"\${DISTDIR}/\${FILE}\" \"\${URI}\""
143 # Using wget, ratelimiting downloads
144 #FETCHCOMMAND="/usr/bin/wget -t 3 -T 60 --passive-ftp --limit-rate=200k -O \"\${DISTDIR}/\${FILE}\" \"\${URI}\""
145 #RESUMECOMMAND="/usr/bin/wget -c -t 3 -T 60 --passive-ftp --limit-rate=200k -O \"\${DISTDIR}/\${FILE}\" \"\${URI}\""
147 # Lukemftp (BSD ftp):
148 #FETCHCOMMAND="/usr/bin/lukemftp -s -a -o \"\${DISTDIR}/\${FILE}\" \"\${URI}\""
149 #RESUMECOMMAND="/usr/bin/lukemftp -s -a -R -o \"\${DISTDIR}/\${FILE}\" \"\${URI}\""
151 # Portage uses GENTOO_MIRRORS to specify mirrors to use for source retrieval.
152 # The list is a space separated list which is read left to right. If you use
153 # another mirror we highly recommend leaving the default mirror at the end of
154 # the list so that portage will fall back to it if the files cannot be found
155 # on your specified mirror. We _HIGHLY_ recommend that you change this setting
156 # to a nearby mirror by merging and using the 'mirrorselect' tool.
157 #GENTOO_MIRRORS="<your_mirror_here> http://distfiles.gentoo.org http://www.ibiblio.org/pub/Linux/distributions/gentoo"
159 # Portage uses PORTAGE_BINHOST to specify mirrors for prebuilt-binary packages.
160 # The list is a single entry specifying the full address of the directory
161 # serving the tbz2's for your system. Running emerge with either '--getbinpkg'
162 # or '--getbinpkgonly' will cause portage to retrieve the metadata from all
163 # packages in the directory specified, and use that data to determine what will
164 # be downloaded and merged. '-g' or '-gK' are the recommend parameters. Please
165 # consult the man pages and 'emerge --help' for more information. For FTP, the
166 # default connection is passive -- If you require an active connection, affix
167 # an asterisk (*) to the end of the host:port string before the path.
168 #PORTAGE_BINHOST="http://grp.mirror.site/gentoo/grp/1.4/i686/athlon-xp/"
169 # This ftp connection is passive ftp.
170 #PORTAGE_BINHOST="ftp://login:pass@grp.mirror.site/pub/grp/i686/athlon-xp/"
171 # This ftp connection is active ftp.
172 #PORTAGE_BINHOST="ftp://login:pass@grp.mirror.site:21*/pub/grp/i686/athlon-xp/"
174 # Synchronizing Portage
175 # =====================
177 # Each of these settings affects how Gentoo synchronizes your Portage tree.
178 # Synchronization is handled by rsync and these settings allow some control
179 # over how it is done.
181 # SYNC is the server used by rsync to retrieve a localized rsync mirror
182 # rotation. This allows you to select servers that are geographically
183 # close to you, yet still distribute the load over a number of servers.
184 # Please do not single out specific rsync mirrors. Doing so places undue
185 # stress on particular mirrors. Instead you may use one of the following
186 # continent specific rotations:
188 # Default: "rsync://rsync.gentoo.org/gentoo-portage"
189 # North America: "rsync://rsync.namerica.gentoo.org/gentoo-portage"
190 # South America: "rsync://rsync.samerica.gentoo.org/gentoo-portage"
191 # Europe: "rsync://rsync.europe.gentoo.org/gentoo-portage"
192 # Asia: "rsync://rsync.asia.gentoo.org/gentoo-portage"
193 # Australia: "rsync://rsync.au.gentoo.org/gentoo-portage"
195 # If you have multiple Gentoo boxes, it is probably a good idea to have only
196 # one of them sync from the rotations above. The other boxes can then rsync
197 # from the local rsync server, reducing the load on the mirrors.
198 # Instructions for setting up a local rsync server are available here:
199 # http://www.gentoo.org/doc/en/rsync.xml
201 #SYNC="rsync://rsync.gentoo.org/gentoo-portage"
203 # PORTAGE_RSYNC_RETRIES sets the number of times portage will attempt to retrieve
204 # a current portage tree before it exits with an error. This allows
205 # for a more successful retrieval without user intervention most times.
206 # If set to a negative number, then retry until all possible addresses are
208 #PORTAGE_RSYNC_RETRIES="-1"
210 # PORTAGE_RSYNC_EXTRA_OPTS can be used to feed additional options to the rsync
211 # command used by `emerge --sync`. This will not change the default options
212 # which are set by PORTAGE_RSYNC_OPTS (don't change those unless you know
213 # exactly what you're doing).
214 #PORTAGE_RSYNC_EXTRA_OPTS=""
219 # EMERGE_DEFAULT_OPTS allows emerge to act as if certain options are
220 # specified on every run. Useful options include --ask, --verbose,
221 # --usepkg and many others. Options that are not useful, such as --help,
223 #EMERGE_DEFAULT_OPTS=""
225 # INSTALL_MASK allows certain files to not be installed into your file system.
226 # This is useful when you wish to filter out a certain set of files from
227 # ever being installed, such as INSTALL.gz or TODO.gz
230 # MAKEOPTS provides extra options that may be passed to 'make' when a
231 # program is compiled. Presently the only use is for specifying
232 # the number of parallel makes (-j) to perform. The suggested number
233 # for parallel makes is CPUs+1.
236 # PORTAGE_NICENESS provides a default increment to emerge's niceness level.
237 # Note: This is an increment. Running emerge in a niced environment will
238 # reduce it further. Default is unset.
241 # PORTAGE_IONICE_COMMAND provides a command for portage to call in order to
242 # adjust the io priority of portage and it's subprocesses. Default is
244 #PORTAGE_IONICE_COMMAND="ionice -c 3 -p \${PID}"
246 # AUTOCLEAN enables portage to automatically clean out older or overlapping
247 # packages from the system after every successful merge. This is the
248 # same as running 'emerge -c' after every merge. Set with: "yes" or "no".
249 # This does not affect the unpacked source. See 'noclean' below.
251 # Warning: AUTOCLEAN="no" can cause serious problems due to overlapping
252 # packages. Do not use it unless absolutely necessary!
255 # FEATURES defines actions portage takes by default. This is an incremental
256 # variable. See the make.conf(5) man page for a complete list of supported
257 # values and their respective meanings.
258 #FEATURES="ccache distcc installsources \
259 # splitdebug test userpriv usersandbox"
261 # CCACHE_SIZE and CCACHE_DIR are used to control the behavior of ccache, and
262 # and are only used if "ccache" is in FEATURES.
264 # CCACHE_SIZE sets the space limitations for ccache. The default size is
265 # "2G", or 2 gigabytes. Units are specified with 'G', 'M', or 'K'.
269 # CCACHE_DIR sets the ccache path. If not specified, portage will default
270 # to "${PORTAGE_TMPDIR}/ccache".
272 # Note that to display ccache statistics outside of portage, you must
273 # remember to give the correct path to the cache.
275 # $ CCACHE_DIR=/var/tmp/ccache ccache -s
277 #CCACHE_DIR="${PORTAGE_TMPDIR}/ccache"
279 # DISTCC_DIR sets the temporary space used by distcc.
280 #DISTCC_DIR="${PORTAGE_TMPDIR}/.distcc"
282 # logging related variables:
283 # PORTAGE_ELOG_CLASSES: selects messages to be logged, possible values are:
284 # info, warn, error, log, qa, *
285 # Warning: commenting this will disable elog
286 PORTAGE_ELOG_CLASSES="log warn error"
288 # PORTAGE_ELOG_SYSTEM: selects the module(s) to process the log messages. Modules
289 # included in portage are (empty means logging is disabled):
290 # echo (display messages again when emerge exits)
291 # save (saves one log per package in $PORT_LOGDIR/elog,
292 # /var/log/portage/elog if $PORT_LOGDIR is unset)
293 # custom (passes all messages to $PORTAGE_ELOG_COMMAND)
294 # syslog (sends all messages to syslog)
295 # mail (send all messages to the mailserver defined
296 # in $PORTAGE_ELOG_MAILURI)
297 # save_summary (like "save" but merges all messages
298 # in $PORT_LOGDIR/elog/summary.log,
299 # /var/log/portage/elog/summary.log if
300 # $PORT_LOGDIR is unset)
301 # mail_summary (like "mail" but sends all messages in
302 # a single mail when emerge exits)
303 # To use elog you should enable at least one module
304 # The module name may be followed by a colon and a comma
305 # separated list of loglevels to override PORTAGE_ELOG_CLASSES
306 # for this module (e.g.
307 # PORTAGE_ELOG_SYSTEM="mail:warn,error syslog:* save")
308 #PORTAGE_ELOG_SYSTEM="save mail"
310 # PORTAGE_ELOG_COMMAND: only used with the "custom" logging module. Specifies a command
311 # to process log messages. Two variables are expanded:
312 # ${PACKAGE} - expands to the cpv entry of the processed
313 # package (see $PVR in ebuild(5))
314 # ${LOGFILE} - absolute path to the logfile
315 # Both variables have to be quoted with single quotes
316 #PORTAGE_ELOG_COMMAND="/path/to/logprocessor -p '\${PACKAGE}' -f '\${LOGFILE}'"
318 # PORTAGE_ELOG_MAILURI: this variable holds all important settings for the mail
319 # module. In most cases listing the recipient address and
320 # the receiving mailserver should be sufficient, but you can
321 # also use advanced settings like authentication or TLS. The
323 # address [[user:passwd@]mailserver[:port]]
325 # address: recipient address
326 # user: username for smtp auth (defaults to none)
327 # passwd: password for smtp auth (defaults to none)
328 # mailserver: smtp server that should be used to deliver the mail (defaults to localhost)
329 # alternatively this can also be a the path to a sendmail binary if you don't want to use smtp
330 # port: port to use on the given smtp server (defaults to 25, values > 100000 indicate that starttls should be used on (port-100000))
332 #PORTAGE_ELOG_MAILURI="root@localhost localhost" (this is also the default setting)
333 #PORTAGE_ELOG_MAILURI="user@some.domain mail.some.domain" (sends mails to user@some.domain using the mailserver mail.some.domain)
334 #PORTAGE_ELOG_MAILURI="user@some.domain user:secret@mail.some.domain:100465" (this is left uncommented as a reader exercise ;)
336 # PORTAGE_ELOG_MAILFROM: you can set the from-address of logmails with this variable,
337 # if unset mails are sent by "portage" (this default may fail
338 # in some environments).
339 #PORTAGE_ELOG_MAILFROM="portage@some.domain"
341 # PORTAGE_ELOG_MAILSUBJECT: template string to be used as subject for logmails. The following
342 # variables are expanded:
343 # ${ACTION} - merged, unmerged, or unknown
344 # ${PACKAGE} - see description of PORTAGE_ELOG_COMMAND
345 # ${HOST} - FQDN of the host portage is running on
346 #PORTAGE_ELOG_MAILSUBJECT="[portage] ebuild log for \${PACKAGE} on \${HOST}"