Handbook Talk:AMD64/Portage/Files

From Gentoo Wiki
Jump to:navigation Jump to:search
Note
Before creating a discussion or leaving a comment, please read about using talk pages. To create a new discussion, click here. Comments on an existing discussion should be signed using ~~~~:
A comment [[User:Larry|Larry]] 13:52, 13 May 2024 (UTC)
: A reply [[User:Sally|Sally]] 02:43, 26 January 2025 (UTC)
:: Your reply ~~~~

Small fixes

Talk status
This discussion is done as of April 20th, 2017.

Some small fixes:

  • The Path templated should be added around "repos.conf" in the following sentence: "This is defined by the default repos.conf file found at [...]"
  • "Portage' configurations are set in the make.defaults files of the profile and all parent profiles." should become "Portage's configurations..."

Fturco (talk) 11:47, 18 April 2017 (UTC)

Done, thanks. --SwifT (talk) 16:23, 20 April 2017 (UTC)

Suggested changes

Talk status
This discussion is done as of 2024-10-19.

"Portage files" section

"Configuration directives" section

Proposed changes - Please make edits here until a final revision is agreed upon.

Portage's variables Portage and what they mean are described later.
Proposed changes - Please make edits here until a final revision is agreed upon.

For more information, read the /usr/share/portage/config/make.conf.example file. As the name implies, this is merely an example file - Portage does not read it.

"Profile-specific information" section

Proposed changes - Please make edits here until a final revision is agreed upon.

This is actually a symbolic link to a profile - by default, one inside /var/db/repos/gentoo/profiles/, although one can create profiles elsewhere and point to them.

"User-specific configuration" section

Proposed changes - Please make edits here until a final revision is agreed upon.

When Portage's behavior needs to be changed, certain files inside /etc/portage/ will need to be modified. Using files within /etc/portage/ is highly recommended; overriding Portage's behavior through environment variables is highly discouraged.
Proposed changes - Please make edits here until a final revision is agreed upon.

These don't have to be files; they can also be directories that contain one or more file(s) with the relevant settings. More information about the /etc/portage/ directory, together with a full list of files that can be created, can be found in the Portage man page:

"Changing Portage file and directory locations" section

Proposed changes - Please make edits here until a final revision is agreed upon.

However, Portage uses many other locations, for various purposes: package builds, source code storage, repository locations, and so on. All of these have default locations, but can be altered to personal taste through /etc/portage/make.conf.
Proposed changes - Please make edits here until a final revision is agreed upon.

This Handbook isn't meant to be used as a reference though - for details, please refer to the portage and make.conf man pages:

"Storing files" section

"Gentoo ebuild repository" section

Proposed changes - Please make edits here until a final revision is agreed upon.

The default location of the Gentoo ebuild repository is /var/db/repos/gentoo.
Proposed changes - Please make edits here until a final revision is agreed upon.

After changing the location setting in /etc/portage/repos.conf/gentoo.conf, it is recommended to also alter the following variables in /etc/portage/make.conf, since - due to how Portage handle variables - they will not notice the location change: PKGDIR, DISTDIR, and RPMDIR.

"Logging features" section

"Ebuild logging" section

Proposed changes - Please make edits here until a final revision is agreed upon.

If PORT_LOGDIR is not set, there will be no build logs stored in the enabled logging system (although users may receive some logs from the new elog support.
Proposed changes - Please make edits here until a final revision is agreed upon.

This is where users can define the kinds of messages to be logged. The variable's value can be any space-separated combination of info, warn, error, log, and qa.

(And the relevant terms in the subsequent dot points surrounded by <code> tags accordingly.)

Proposed changes - Please make edits here until a final revision is agreed upon.

Any space-separated combination of save, custom, syslog, mail, save_summary, and mail_summary can be used.

(And the relevant terms in the following dot points surrounded by <code> tags accordingly.)

Proposed changes - Please make edits here until a final revision is agreed upon.

This is only used when the custom module is enabled.

Are the backslashes required before the dollar signs in the example PORTAGE_ELOG_COMMAND definition?

Proposed changes - Please make edits here until a final revision is agreed upon.

This contains settings for the mail module, such as address, user, password, mail server, and port number.

Are the backslashes required before the dollar signs in the example PORTAGE_ELOG_MAILSUBJECT definition?

Thanks! Added in Special:Diff/1271698/1316755
--csfore (talk) 17:24, 19 October 2024 (UTC)