|
Lines 115-128
Link Here
|
| 115 |
# |
115 |
# |
| 116 |
# DISTDIR is where all of the source code tarballs will be placed for |
116 |
# DISTDIR is where all of the source code tarballs will be placed for |
| 117 |
# emerges. The source code is maintained here unless you delete |
117 |
# emerges. The source code is maintained here unless you delete |
| 118 |
# it. The entire repository of tarballs for gentoo is 9G. This is |
118 |
# it. The entire repository of tarballs for Gentoo is 9G. This is |
| 119 |
# considerably more than any user will ever download. 2-3G is |
119 |
# considerably more than any user will ever download. 2-3G is |
| 120 |
# a large DISTDIR. |
120 |
# a large DISTDIR. |
| 121 |
#DISTDIR=${PORTDIR}/distfiles |
121 |
#DISTDIR=${PORTDIR}/distfiles |
| 122 |
# |
122 |
# |
| 123 |
# PKGDIR is the location of binary packages that you can have created |
123 |
# PKGDIR is the location of binary packages that you can have created |
| 124 |
# with '--buildpkg' or '-b' while emerging a package. This can get |
124 |
# with '--buildpkg' or '-b' while emerging a package. This can get |
| 125 |
# upto several hundred megs, or even a few gigs. |
125 |
# up to several hundred megs, or even a few gigs. |
| 126 |
#PKGDIR=${PORTDIR}/packages |
126 |
#PKGDIR=${PORTDIR}/packages |
| 127 |
# |
127 |
# |
| 128 |
# PORT_LOGDIR is the location where portage will store all the logs it |
128 |
# PORT_LOGDIR is the location where portage will store all the logs it |
|
Lines 273-279
Link Here
|
| 273 |
# developers as well. |
273 |
# developers as well. |
| 274 |
# |
274 |
# |
| 275 |
# 'assume-digests' |
275 |
# 'assume-digests' |
| 276 |
# when commiting work to cvs with repoman(1), assume that all |
276 |
# when committing work to cvs with repoman(1), assume that all |
| 277 |
# existing SRC_URI digests are correct. This feature also |
277 |
# existing SRC_URI digests are correct. This feature also |
| 278 |
# affects digest generation via ebuild(1) and emerge(1) (emerge |
278 |
# affects digest generation via ebuild(1) and emerge(1) (emerge |
| 279 |
# generates digests only when the 'digest' feature is enabled). |
279 |
# generates digests only when the 'digest' feature is enabled). |
|
Lines 307-313
Link Here
|
| 307 |
# from a merge. |
307 |
# from a merge. |
| 308 |
# 'keepwork' prevents the clean phase from deleting the WORKDIR. |
308 |
# 'keepwork' prevents the clean phase from deleting the WORKDIR. |
| 309 |
# 'test' causes ebuilds to perform testing phases if they are capable |
309 |
# 'test' causes ebuilds to perform testing phases if they are capable |
| 310 |
# of it. Some packages support this automaticaly via makefiles. |
310 |
# of it. Some packages support this automatically via makefiles. |
| 311 |
# 'metadata-transfer' |
311 |
# 'metadata-transfer' |
| 312 |
# automatically perform a metadata transfer when `emerge --sync` |
312 |
# automatically perform a metadata transfer when `emerge --sync` |
| 313 |
# is run. |
313 |
# is run. |
|
Lines 323-328
Link Here
|
| 323 |
# 'sandbox' enables sandboxing when running emerge and ebuild. |
323 |
# 'sandbox' enables sandboxing when running emerge and ebuild. |
| 324 |
# 'strict' causes portage to react strongly to conditions that are |
324 |
# 'strict' causes portage to react strongly to conditions that are |
| 325 |
# potentially dangerous, like missing/incorrect Manifest files. |
325 |
# potentially dangerous, like missing/incorrect Manifest files. |
|
|
326 |
# 'stricter' causes portage to react strongly to conditions that may |
| 327 |
# conflict with system security provisions (for example |
| 328 |
# textrels, executable stacks). |
| 326 |
# 'userfetch' when portage is run as root, drop privileges to |
329 |
# 'userfetch' when portage is run as root, drop privileges to |
| 327 |
# portage:portage during the fetching of package sources. |
330 |
# portage:portage during the fetching of package sources. |
| 328 |
# 'userpriv' allows portage to drop root privileges while it is compiling, |
331 |
# 'userpriv' allows portage to drop root privileges while it is compiling, |
|
Lines 385-391
Link Here
|
| 385 |
# Examples: |
388 |
# Examples: |
| 386 |
#PORTAGE_ELOG_MAILURI="root@localhost localhost" (this is also the default setting) |
389 |
#PORTAGE_ELOG_MAILURI="root@localhost localhost" (this is also the default setting) |
| 387 |
#PORTAGE_ELOG_MAILURI="user@some.domain mail.some.domain" (sends mails to user@some.domain using the mailserver mail.some.domain) |
390 |
#PORTAGE_ELOG_MAILURI="user@some.domain mail.some.domain" (sends mails to user@some.domain using the mailserver mail.some.domain) |
| 388 |
#PORTAGE_ELOG_MAILURI="user@some.domain user:secret@mail.some.domain:100465" (this is left uncommented as a reader excercise ;) |
391 |
#PORTAGE_ELOG_MAILURI="user@some.domain user:secret@mail.some.domain:100465" (this is left uncommented as a reader exercise ;) |
| 389 |
|
392 |
|
| 390 |
# PORTAGE_ELOG_MAILFROM: you can set the from-address of logmails with this variable, |
393 |
# PORTAGE_ELOG_MAILFROM: you can set the from-address of logmails with this variable, |
| 391 |
# if unset mails are sent by "portage" (this default may fail |
394 |
# if unset mails are sent by "portage" (this default may fail |
|
Lines 393-399
Link Here
|
| 393 |
#PORTAGE_ELOG_MAILFROM="portage@some.domain" |
396 |
#PORTAGE_ELOG_MAILFROM="portage@some.domain" |
| 394 |
|
397 |
|
| 395 |
# PORTAGE_ELOG_MAILSUBJECT: template string to be used as subject for logmails. The following |
398 |
# PORTAGE_ELOG_MAILSUBJECT: template string to be used as subject for logmails. The following |
| 396 |
# variables are exanded: |
399 |
# variables are expanded: |
| 397 |
# ${PACKAGE} - see description of PORTAGE_ELOG_COMMAND |
400 |
# ${PACKAGE} - see description of PORTAGE_ELOG_COMMAND |
| 398 |
# ${HOST} - FQDN of the host portage is running on |
401 |
# ${HOST} - FQDN of the host portage is running on |
| 399 |
#PORTAGE_ELOG_MAILSUBJECT="package \${PACKAGE} merged on \${HOST} with notice" |
402 |
#PORTAGE_ELOG_MAILSUBJECT="package \${PACKAGE} merged on \${HOST} with notice" |
