From 8a6434339da2074ecf0b0f2cbf273bdcf44345ae Mon Sep 17 00:00:00 2001 From: Christian Becke Date: Wed, 2 Aug 2023 12:47:51 +0200 Subject: [PATCH] porage(5): fix description of volatile attribute Signed-off-by: Christian Becke --- man/portage.5 | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/man/portage.5 b/man/portage.5 index 4bae67720..1c0ce22bd 100644 --- a/man/portage.5 +++ b/man/portage.5 @@ -1265,11 +1265,11 @@ sync\-openpgp\-key\-path setting. Defaults to no, false. Specifies whether a repository is volatile. Volatile repositories are assumed to contain changes made outside of Portage. This prohibits optimizations from occurring by assuming the integrity of the repository -and its caches may be violated. Disabling this option allows local changes to -be made to the repository for e.g. development safely. For git-synced -repositories, Portage will not perform destructive operations. -Per default, repositories are considered volatile if their directory is owned -by either 'root' or 'portage' and if it is under /var/db/repos. Otherwise, +and its caches may be violated. Enabling this option allows local changes to +be made to the repository for e.g. development safely. When enabled, Portage +will not perform destructive operations for git-synced repositories. Per +default, repositories are considered volatile if their directory is not owned +by either 'root' or 'portage' or if it is not under /var/db/repos. Otherwise, the repository is considered non volatile. .TP -- 2.41.0