1 # Copyright 1999-2006 Gentoo Foundation
2 # Distributed under the terms of the GNU General Public License v2
4 # Contains local system settings for Portage system
6 # Please review 'man make.conf' for more information.
8 # Build-time functionality
9 # ========================
11 # The USE variable is used to enable optional build-time functionality. For
12 # example, quite a few packages have optional X, gtk or GNOME functionality
13 # that can only be enabled or disabled at compile-time. Gentoo Linux has a
14 # very extensive set of USE variables described in our USE variable HOWTO at
15 # http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=1
17 # The available list of use flags with descriptions is in your portage tree.
18 # Use 'less' to view them: --> less /usr/portage/profiles/use.desc <--
20 # 'ufed' is an ncurses/dialog interface available in portage to make handling
21 # useflags for you. 'emerge app-portage/ufed'
24 #USE="X gtk gnome -alsa"
26 # Host and optimization settings
27 # ==============================
29 # For optimal performance, enable a CFLAGS setting appropriate for your CPU.
31 # Please note that if you experience strange issues with a package, it may be
32 # due to gcc's optimizations interacting in a strange way. Please test the
33 # package (and in some cases the libraries it uses) at default optimizations
34 # before reporting errors to developers.
36 # Please refer to the GCC manual for a list of possible values.
40 # If you set a CFLAGS above, then this line will set your default C++ flags to
47 # Gentoo is using a new masking system to allow for easier stability testing
48 # on packages. KEYWORDS are used in ebuilds to mask and unmask packages based
49 # on the platform they are set for. A special form has been added that
50 # indicates packages and revisions that are expected to work, but have not yet
51 # been approved for the stable set. '~arch' is a superset of 'arch' which
52 # includes the unstable, in testing, packages. Users of the 'x86' architecture
53 # would add '~x86' to ACCEPT_KEYWORDS to enable unstable/testing packages.
54 # '~ppc', '~sparc' are the unstable KEYWORDS for their respective platforms.
56 # Please note that this is not for development, alpha, beta, nor cvs release
57 # packages. "Broken" packages will not be added to testing and should not be
58 # requested to be added. Alternative routes are available to developers
59 # for experimental packages, and it is at their discretion to use them.
61 # DO NOT PUT ANYTHING BUT YOUR SPECIFIC ~ARCHITECTURE IN THE LIST.
62 # IF YOU ARE UNSURE OF YOUR ARCH, OR THE IMPLICATIONS, DO NOT MODIFY THIS.
64 #ACCEPT_KEYWORDS="~arch"
69 # Each of these settings controls an aspect of portage's storage and file
70 # system usage. If you change any of these, be sure it is available when
71 # you try to use portage. *** DO NOT INCLUDE A TRAILING "/" ***
73 # PORTAGE_TMPDIR is the location portage will use for compilations and
74 # temporary storage of data. This can get VERY large depending upon
75 # the application being installed.
76 #PORTAGE_TMPDIR=/var/tmp
78 # PORTDIR is the location of the portage tree. This is the repository
79 # for all profile information as well as all ebuilds. If you change
80 # this, you must update your /etc/make.profile symlink accordingly.
83 # DISTDIR is where all of the source code tarballs will be placed for
84 # emerges. The source code is maintained here unless you delete
85 # it. The entire repository of tarballs for gentoo is 9G. This is
86 # considerably more than any user will ever download. 2-3G is
88 #DISTDIR=${PORTDIR}/distfiles
90 # PKGDIR is the location of binary packages that you can have created
91 # with '--buildpkg' or '-b' while emerging a package. This can get
92 # upto several hundred megs, or even a few gigs.
93 #PKGDIR=${PORTDIR}/packages
95 # PORT_LOGDIR is the location where portage will store all the logs it
96 # creates from each individual merge. They are stored as NNNN-$PF.log
97 # in the directory specified. This is disabled until you enable it by
98 # providing a directory. Permissions will be modified as needed IF the
99 # directory exists, otherwise logging will be disabled. NNNN is the
100 # increment at the time the log is created. Logs are thus sequential.
101 #PORT_LOGDIR=/var/log/portage
103 # PORTDIR_OVERLAY is a directory where local ebuilds may be stored without
104 # concern that they will be deleted by rsync updates. Default is not
106 #PORTDIR_OVERLAY=/usr/local/portage
111 # If you need to set a proxy for wget or lukemftp, add the appropriate "export
112 # ftp_proxy=<proxy>" and "export http_proxy=<proxy>" lines to /etc/profile if
113 # all users on your system should use them.
115 # Portage uses wget by default. Here are some settings for some alternate
116 # downloaders -- note that you need to merge these programs first before they
119 # Default fetch command (5 tries, passive ftp for firewall compatibility)
120 #FETCHCOMMAND="/usr/bin/wget -t 5 -T 60 --passive-ftp \${URI} -P \${DISTDIR}"
121 #RESUMECOMMAND="/usr/bin/wget -c -t 5 -T 60 --passive-ftp \${URI} -P \${DISTDIR}"
123 # Using wget, ratelimiting downloads
124 #FETCHCOMMAND="/usr/bin/wget -t 5 -T 60 --passive-ftp --limit-rate=200k \${URI} -P \${DISTDIR}"
125 #RESUMECOMMAND="/usr/bin/wget -c -t 5 -T 60 --passive-ftp --limit-rate=200k \${URI} -P \${DISTDIR}"
127 # Lukemftp (BSD ftp):
128 #FETCHCOMMAND="/usr/bin/lukemftp -s -a -o \${DISTDIR}/\${FILE} \${URI}"
129 #RESUMECOMMAND="/usr/bin/lukemftp -s -a -R -o \${DISTDIR}/\${FILE} \${URI}"
131 # Portage uses GENTOO_MIRRORS to specify mirrors to use for source retrieval.
132 # The list is a space separated list which is read left to right. If you use
133 # another mirror we highly recommend leaving the default mirror at the end of
134 # the list so that portage will fall back to it if the files cannot be found
135 # on your specified mirror. We _HIGHLY_ recommend that you change this setting
136 # to a nearby mirror by merging and using the 'mirrorselect' tool.
137 #GENTOO_MIRRORS="<your_mirror_here> http://distfiles.gentoo.org http://www.ibiblio.org/pub/Linux/distributions/gentoo"
139 # Portage uses PORTAGE_BINHOST to specify mirrors for prebuilt-binary packages.
140 # The list is a single entry specifying the full address of the directory
141 # serving the tbz2's for your system. Running emerge with either '--getbinpkg'
142 # or '--getbinpkgonly' will cause portage to retrieve the metadata from all
143 # packages in the directory specified, and use that data to determine what will
144 # be downloaded and merged. '-g' or '-gK' are the recommend parameters. Please
145 # consult the man pages and 'emerge --help' for more information. For FTP, the
146 # default connection is passive -- If you require an active connection, affix
147 # an asterisk (*) to the end of the host:port string before the path.
148 #PORTAGE_BINHOST="http://grp.mirror.site/gentoo/grp/1.4/i686/athlon-xp/"
149 # This ftp connection is passive ftp.
150 #PORTAGE_BINHOST="ftp://login:pass@grp.mirror.site/pub/grp/i686/athlon-xp/"
151 # This ftp connection is active ftp.
152 #PORTAGE_BINHOST="ftp://login:pass@grp.mirror.site:21*/pub/grp/i686/athlon-xp/"
154 # Synchronizing Portage
155 # =====================
157 # Each of these settings affects how Gentoo synchronizes your Portage tree.
158 # Synchronization is handled by rsync and these settings allow some control
159 # over how it is done.
161 # SYNC is the server used by rsync to retrieve a localized rsync mirror
162 # rotation. This allows you to select servers that are geographically
163 # close to you, yet still distribute the load over a number of servers.
164 # Please do not single out specific rsync mirrors. Doing so places undue
165 # stress on particular mirrors. Instead you may use one of the following
166 # continent specific rotations:
168 # Default: "rsync://rsync.gentoo.org/gentoo-portage"
169 # North America: "rsync://rsync.namerica.gentoo.org/gentoo-portage"
170 # South America: "rsync://rsync.samerica.gentoo.org/gentoo-portage"
171 # Europe: "rsync://rsync.europe.gentoo.org/gentoo-portage"
172 # Asia: "rsync://rsync.asia.gentoo.org/gentoo-portage"
173 # Australia: "rsync://rsync.au.gentoo.org/gentoo-portage"
175 # If you have multiple Gentoo boxes, it is probably a good idea to have only
176 # one of them sync from the rotations above. The other boxes can then rsync
177 # from the local rsync server, reducing the load on the mirrors.
178 # Instructions for setting up a local rsync server are available here:
179 # http://www.gentoo.org/doc/en/rsync.xml
181 #SYNC="rsync://rsync.gentoo.org/gentoo-portage"
183 # PORTAGE_RSYNC_RETRIES sets the number of times portage will attempt to retrieve
184 # a current portage tree before it exits with an error. This allows
185 # for a more successful retrieval without user intervention most times.
186 #PORTAGE_RSYNC_RETRIES="3"
188 # PORTAGE_RSYNC_EXTRA_OPTS can be used to feed additional options to the rsync
189 # command used by `emerge --sync`. This will not change the default options
190 # which are set by PORTAGE_RSYNC_OPTS (don't change those unless you know
191 # exactly what you're doing).
192 #PORTAGE_RSYNC_EXTRA_OPTS=""
197 # EMERGE_DEFAULT_OPTS allows emerge to act as if certain options are
198 # specified on every run. Useful options include --ask, --verbose,
199 # --usepkg and many others. Options that are not useful, such as --help,
201 #EMERGE_DEFAULT_OPTS=""
203 # INSTALL_MASK allows certain files to not be installed into your file system.
204 # This is useful when you wish to filter out a certain set of files from
205 # ever being installed, such as INSTALL.gz or TODO.gz
208 # MAKEOPTS provides extra options that may be passed to 'make' when a
209 # program is compiled. Presently the only use is for specifying
210 # the number of parallel makes (-j) to perform. The suggested number
211 # for parallel makes is CPUs+1.
214 # PORTAGE_NICENESS provides a default increment to emerge's niceness level.
215 # Note: This is an increment. Running emerge in a niced environment will
216 # reduce it further. Default is unset.
219 # AUTOCLEAN enables portage to automatically clean out older or overlapping
220 # packages from the system after every successful merge. This is the
221 # same as running 'emerge -c' after every merge. Set with: "yes" or "no".
222 # This does not affect the unpacked source. See 'noclean' below.
224 # Warning: AUTOCLEAN="no" can cause serious problems due to overlapping
225 # packages. Do not use it unless absolutely necessary!
228 # PORTAGE_TMPFS is a location where portage may create temporary files.
229 # If specified, portage will use this directory whenever possible
230 # for all rapid operations such as lockfiles and transient data.
231 # It is _highly_ recommended that this be a tmpfs or ramdisk. Do not
232 # set this to anything that does not give a significant performance
233 # enhancement and proper FS compliance for locks and read/write.
234 # /dev/shm is a glibc mandated tmpfs, and should be a reasonable
235 # setting for all linux kernel+glibc based systems.
236 #PORTAGE_TMPFS="/dev/shm"
238 # FEATURES are settings that affect the functionality of portage. Most of
239 # these settings are for developer use, but some are available to non-
240 # developers as well.
243 # when commiting work to cvs with repoman(1), assume that all
244 # existing SRC_URI digests are correct. This feature also
245 # affects digest generation via ebuild(1) and emerge(1) (emerge
246 # generates digests only when the 'digest' feature is enabled).
247 # 'buildpkg' causes binary packages to be created of all packages that
249 # 'ccache' enables ccache support via CC.
250 # 'confcache' enable confcache support; speeds up autotool based configure
252 # 'collision-protect'
253 # prevents packages from overwriting files that are owned by
254 # another package or by no package at all.
255 # 'cvs' causes portage to enable all cvs features (commits, adds),
256 # and to apply all USE flags in SRC_URI for digests -- for
258 # 'digest' autogenerate digests for packages when running the emerge(1)
259 # command. If the 'assume-digests' feature is also enabled then
260 # existing SRC_URI digests will be reused whenever they are
262 # 'distcc' enables distcc support via CC.
263 # 'distlocks' enables distfiles locking using fcntl or hardlinks. This
264 # is enabled by default. Tools exist to help clean the locks
265 # after crashes: /usr/lib/portage/bin/clean_locks.
266 # 'fixpackages' allows portage to fix binary packages that are stored in
267 # PKGDIR. This can consume a lot of time. 'fixpackages' is
268 # also a script that can be run at any given time to force
270 # 'gpg' enables basic verification of Manifest files using gpg.
271 # This features is UNDER DEVELOPMENT and reacts to features
272 # of strict and severe. Heavy use of gpg sigs is coming.
273 # 'keeptemp' prevents the clean phase from deleting the temp files ($T)
275 # 'keepwork' prevents the clean phase from deleting the WORKDIR.
276 # 'test' causes ebuilds to perform testing phases if they are capable
277 # of it. Some packages support this automaticaly via makefiles.
278 # 'metadata-transfer'
279 # automatically perform a metadata transfer when `emerge --sync`
281 # 'noauto' causes ebuild to perform only the action requested and
282 # not any other required actions like clean or unpack -- for
283 # debugging purposes only.
284 # 'noclean' prevents portage from removing the source and temporary files
285 # after a merge -- for debugging purposes only.
286 # 'nostrip' prevents the stripping of binaries.
287 # 'notitles' disables xterm titlebar updates (which contain status info).
289 # do fetching in parallel to compilation
290 # 'sandbox' enables sandboxing when running emerge and ebuild.
291 # 'strict' causes portage to react strongly to conditions that are
292 # potentially dangerous, like missing/incorrect Manifest files.
293 # 'userfetch' when portage is run as root, drop privileges to
294 # portage:portage during the fetching of package sources.
295 # 'userpriv' allows portage to drop root privileges while it is compiling,
296 # as a security measure. As a side effect this can remove
297 # sandbox access violations for users.
298 # 'usersandbox' enables sandboxing while portage is running under userpriv.
299 #FEATURES="sandbox buildpkg ccache distcc userpriv usersandbox notitles noclean noauto cvs keeptemp keepwork"
300 #FEATURES="sandbox ccache distcc distlocks"
302 # CCACHE_SIZE sets the space use limitations for ccache. The default size is
303 # 2G, and will be set if not defined otherwise and ccache is in features.
304 # Portage will set the default ccache dir if it is not present in the
305 # user's environment, for userpriv it sets: ${PORTAGE_TMPDIR}/ccache
306 # (/var/tmp/ccache), and for regular use the default is /root/.ccache.
307 # Sizes are specified with 'G' 'M' or 'K'.
308 # '2G' for 2 gigabytes, '2048M' for 2048 megabytes (same as 2G).
311 # DISTCC_DIR sets the temporary space used by distcc.
312 #DISTCC_DIR="${PORTAGE_TMPDIR}/.distcc"
314 # logging related variables:
315 # PORTAGE_ELOG_CLASSES: selects messages to be logged, possible values are:
316 # info, warn, error, log
317 # Warning: commenting this will disable elog
318 PORTAGE_ELOG_CLASSES="warn error log"
320 # PORTAGE_ELOG_SYSTEM: selects the module(s) to process the log messages. Modules
321 # included in portage are (empty means logging is disabled):
322 # save (saves one log per package in $PORT_LOGDIR/elog,
323 # /var/log/portage/elog if $PORT_LOGDIR is unset)
324 # custom (passes all messages to $PORTAGE_ELOG_COMMAND)
325 # syslog (sends all messages to syslog)
326 # mail (send all messages to the mailserver defined
327 # in $PORTAGE_ELOG_MAILURI)
328 # save_summary (like "save" but merges all messages
329 # in $PORT_LOGDIR/elog/summary.log,
330 # /var/log/portage/elog/summary.log if
331 # $PORT_LOGDIR is unset)
332 # mail_summary (like "mail" but sends all messages in
333 # a single mail when emerge exits)
334 # To use elog you should enable at least one module
335 #PORTAGE_ELOG_SYSTEM="save mail"
337 # PORTAGE_ELOG_COMMAND: only used with the "custom" logging module. Specifies a command
338 # to process log messages. Two variables are expanded:
339 # ${PACKAGE} - expands to the cpv entry of the processed
340 # package (see $PVR in ebuild(5))
341 # ${LOGFILE} - absolute path to the logfile
342 # Both variables have to be quoted with single quotes
343 #PORTAGE_ELOG_COMMAND="/path/to/logprocessor -p '\${PACKAGE}' -f '\${LOGFILE}'"
345 # PORTAGE_ELOG_MAILURI: this variable holds all important settings for the mail
346 # module. In most cases listing the recipient address and
347 # the receiving mailserver should be sufficient, but you can
348 # also use advanced settings like authentication or TLS. The
350 # address [[user:passwd@]mailserver[:port]]
352 # address: recipient address
353 # user: username for smtp auth (defaults to none)
354 # passwd: password for smtp auth (defaults to none)
355 # mailserver: smtp server that should be used to deliver the mail (defaults to localhost)
356 # alternatively this can also be a the path to a sendmail binary if you don't want to use smtp
357 # port: port to use on the given smtp server (defaults to 25, values > 100000 indicate that starttls should be used on (port-100000))
359 #PORTAGE_ELOG_MAILURI="root@localhost localhost" (this is also the default setting)
360 #PORTAGE_ELOG_MAILURI="user@some.domain mail.some.domain" (sends mails to user@some.domain using the mailserver mail.some.domain)
361 #PORTAGE_ELOG_MAILURI="user@some.domain user:secret@mail.some.domain:100465" (this is left uncommented as a reader excercise ;)
363 # PORTAGE_ELOG_MAILFROM: you can set the from-address of logmails with this variable,
364 # if unset mails are sent by "portage" (this default may fail
365 # in some environments).
366 #PORTAGE_ELOG_MAILFROM="portage@some.domain"
368 # PORTAGE_ELOG_MAILSUBJECT: template string to be used as subject for logmails. The following
369 # variables are exanded:
370 # ${PACKAGE} - see description of PORTAGE_ELOG_COMMAND
371 # ${HOST} - FQDN of the host portage is running on
372 #PORTAGE_ELOG_MAILSUBJECT="package \${PACKAGE} merged on \${HOST} with notice"