commit: cc4250c9d0f6567db3f742d62cd3eb768f417a18 Author: Sam James <sam <AT> gentoo <DOT> org> AuthorDate: Fri Jan 13 07:40:15 2023 +0000 Commit: Sam James <sam <AT> gentoo <DOT> org> CommitDate: Fri Jan 13 07:41:52 2023 +0000 URL: https://gitweb.gentoo.org/proj/portage.git/commit/?id=cc4250c9
NEWS: explain how 'volatile' default is determined See: ef123a214708c85f9802f2a649b93137fd2ee3be See: https://github.com/gentoo/portage/pull/961#pullrequestreview-1222025162 Signed-off-by: Sam James <sam <AT> gentoo.org> NEWS | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/NEWS b/NEWS index 60782fbb8..4e27411ee 100644 --- a/NEWS +++ b/NEWS @@ -63,13 +63,11 @@ Breaking changes: 2. Defaulted to sync-depth=clone-depth=1. The motivation here was because of disk space growing unbounded - otherwise. It makes sense when considered within the school of thought / motivation - listed above (prioritising a successful sync and then making an optimisation + otherwise, as a full disk could lead to sync failure. It also makes sense + when considered within the school of thought / motivation listed above + (prioritising a successful sync and then making an optimisation based on how we achieve that). - Further, there was additional motivation to avoid disk usage growing - unbounded (which additionally could lead to a sync failing at some point). - Portage 3.0.42 will now only make a repository shallow if: 1. volatile=yes and it is a new sync (i.e. it was not deep before), or 2. volatile=no and sync-depth is unset in repos.conf. @@ -87,6 +85,10 @@ Breaking changes: by Portage, and Portage will try its best to ensure syncs continue to work. + The default value of 'volatile' is determined as follows: + - If unset and the repository is under /var/db/repos and the repository + exists and it's owned by either 'portage' or 'root', set to yes. + Features: * cnf: make.conf.example.loong: add for the loong arch (bug #884135).
