aboutsummaryrefslogtreecommitdiff
path: root/cnf
Commit message (Collapse)AuthorAgeFilesLines
* Revert "make.globals: Set PORTAGE_USERNAME and PORTAGE_GRPNAME variables"Zac Medico2025-01-111-4/+0
| | | | | | | This reverts commit 5a652b1289830ccb0eb138ef0844a312d9531e0a because it breaks "unprivileged" mode. Signed-off-by: Zac Medico <zmedico@gentoo.org>
* make.globals: Set PORTAGE_USERNAME and PORTAGE_GRPNAME variablesDavid Sardari2025-01-111-0/+4
| | | | | | | | | | | | | | | | "man 5 make.conf" states that "PORTAGE_USERNAME" and "PORTAGE_GRPNAME" default to "portage": - https://github.com/gentoo/portage/blob/597229aff02810764223a4cdd1e8056142d70ed0/man/make.conf.5#L1257-L1261 - https://github.com/gentoo/portage/blob/597229aff02810764223a4cdd1e8056142d70ed0/man/make.conf.5#L1109-L1113 But, the two variables are not set in the files pointed out by "man 5 make.conf": https://github.com/gentoo/portage/blob/597229aff02810764223a4cdd1e8056142d70ed0/man/make.conf.5#L21-L31 This commits solves the discrepancy. Bug: https://bugs.gentoo.org/941977 Signed-off-by: David Sardari <d@duxsco.de> Closes: https://github.com/gentoo/portage/pull/1414 Signed-off-by: Zac Medico <zmedico@gentoo.org>
* update set for "rust-rebuild" to adapt to changes in gentooEli Schwartz2024-11-181-2/+2
| | | | | | | | | | | | | | | The virtual package is deprecated and we use an eclass to depend on an any-of group for the relevant rust compilers. This set no longer does anything without an update. Start checking BDEPEND for the specific rust compilers. Also keep checking for the virtual, so that "rust-rebuild" reports on packages that have not, in fact, been rebuilt yet. Bug: https://bugs.gentoo.org/906044 Closes: https://github.com/gentoo/portage/pull/1399 Signed-off-by: Eli Schwartz <eschwartz@gentoo.org> Signed-off-by: Mike Gilbert <floppym@gentoo.org>
* make.globals: disable FEATURES="sfperms" by defaultMike Gilbert2024-11-101-2/+1
| | | | | | | | Removing the read bit from suid binaries has questionable security benefit, and may cause problems for some software. Bug: https://bugs.gentoo.org/938164 Signed-off-by: Mike Gilbert <floppym@gentoo.org>
* make.globals: add bcachefs_effective.* and bcachefs.* to PORTAGE_XATTR_EXCLUDEFlorian Schmaus2024-07-211-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | Just like btrfs the bcachefs filesystem makes heaviy use of xattrs. In my case emerge --config gentoo-kernel failed with install-xattr: setxattr() failed: Operation not supported A strace revealed setxattr("/boot/efi/8410476acd4b1e12c678fc815c18f551/6.9.5-gentoo-dist/linux", "bcachefs_effective.background_co"..., "zstd", 4, 0) = -1 EOPNOTSUPP (Operation not supported) and indeed, the source file to the install operation was under /usr/src which had background compression enabled. As a result, install-xattr tried to copy the attribute over to the destination file and failed. Signed-off-by: Florian Schmaus <flow@gentoo.org> Closes: https://github.com/gentoo/portage/pull/1346 Signed-off-by: Sam James <sam@gentoo.org>
* meson.build: Install dist-info METADATAZac Medico2024-03-071-0/+3
| | | | | | | | | | | Install dist-info METADATA for pip to resolve dependencies: # pip freeze | grep portage portage==3.0.63 Suggested-by: Eli Schwartz <eschwartz93@gmail.com> Bug: https://bugs.gentoo.org/920330 Signed-off-by: Zac Medico <zmedico@gentoo.org>
* cnf: sets: Migrate @golang-rebuild to dev-lang/goZac Medico2024-02-261-6/+0
| | | | | Bug: https://bugs.gentoo.org/919751 Signed-off-by: Zac Medico <zmedico@gentoo.org>
* cnf: add arch-specific configuration example for arcMatoro Mahri2024-02-091-0/+46
| | | | | Signed-off-by: Matoro Mahri <matoro_gentoo@matoro.tk> Signed-off-by: Sam James <sam@gentoo.org>
* Add merge-wait FEATURES setting enabled by defaultZac Medico2024-01-151-2/+2
| | | | | | | | | | | | | | | | | | Add a new merge-wait FEATURES setting, enabled by default, which prevents packages from being merged while other packages are building. Previously, this behavior was already implemented for packages that satisfy direct or indirect dependencies of the system set. This feature can be disabled only for other packages which do not satisfy direct or indirect dependencies of the system set, in order to trade the possibility of random build failures for greater parallelism. Currently, it is known that having merge-wait disabled can cause "random" build failures for builds using setuptools when setuptools plugins are merged during the build. Bug: https://bugs.gentoo.org/663324 Signed-off-by: Zac Medico <zmedico@gentoo.org>
* Switch default binary package format to gpkgAndreas K. Hüttel2023-12-101-3/+3
| | | | | Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org> Signed-off-by: Sam James <sam@gentoo.org>
* repos.conf: set value of sync-rsync-verify-max-age for ::gentoo to 3Florian Schmaus2023-10-131-1/+1
| | | | | | | | | | | | | | | The value sync-rsync-verify-max-age specifies the default age in days. The current value of 24 is too high for an repo with daily changes like ::gentoo, and was set under the assumption that max-age denotes hours [1]. 1: 8d99acdb3f4f ("rsync: Issue an explicit warning if Manifest timestamp is >24hr old") Signed-off-by: Florian Schmaus <flow@gentoo.org> Fixes: 8d99acdb3f4f ("rsync: Issue an explicit warning if Manifest timestamp is >24hr old") Closes: https://github.com/gentoo/portage/pull/1125 Signed-off-by: Sam James <sam@gentoo.org>
* make.globals: default-on FEATURES=pkgdir-index-trustedJohn Helmert III2023-09-191-1/+1
| | | | | | | | | | | | | | | | | Commit fbbe0cfe29020313ae44fb2a6afa87c2951ae028 indicates that the rationale for having this disabled is to tolerate manual additions/removals of binpkgs in the PKGDIR. I don't think there are many people doing this, so it should be safe to enable this by default for quicker operations with PKGDIR. [sam: This is only used for local operations, we don't reindex remote indexes, so there's no issue with not having indexes be signed (although we do plan on doing that at some point).] Bug: https://bugs.gentoo.org/889300 Signed-off-by: John Helmert III <ajak@gentoo.org> Closes: https://github.com/gentoo/portage/pull/970 Signed-off-by: Sam James <sam@gentoo.org>
* Run PORTAGE_TRUST_HELPER before remote binary package operationsAndreas K. Hüttel2023-09-031-0/+3
| | | | | | | | | | Right now this is somewhat suboptimal because the helper is only called if FEATURES="binpkg-request-signature" is set, but existing signatures are also verified otherwise. Closes: https://github.com/gentoo/portage/pull/1085 Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org> Signed-off-by: Mike Gilbert <floppym@gentoo.org>
* Fix risc vs riscv typo in Meson fileJames Le Cuirot2023-08-031-2/+2
| | | | | Closes: https://github.com/gentoo/portage/pull/1076 Signed-off-by: Sam James <sam@gentoo.org>
* Fix Meson CPU detection for make.confJames Le Cuirot2023-08-031-1/+1
| | | | | | | I used the CPU name rather than the family by mistake. Signed-off-by: James Le Cuirot <chewi@gentoo.org> Signed-off-by: Sam James <sam@gentoo.org>
* Migrate from setuptools to Meson and meson-pythonJames Le Cuirot2023-08-021-0/+144
| | | | | | | | | | | This makes Portage PEP 517 compliant. When building via meson-python, the man pages and logrotate config are no longer included as there seems little point. Bug: https://bugs.gentoo.org/910035 Signed-off-by: James Le Cuirot <chewi@gentoo.org> Signed-off-by: Sam James <sam@gentoo.org>
* SCHEDULING_POLICY: switch to scheduler policy IDs rather than aliases.KARBOWSKI Piotr2023-01-141-6/+6
| | | | | | | | | | | | | | The os.SCHED_* aliases are not reliable enough, the mainline Python lacks deadline, and the pypy lacks them all together. The IDs are not going to change, at most new would arrive, so it is safe to use it as is. By extension, the deadline policy was also added, since those originally were not present in aliases. Bug: https://bugs.gentoo.org/867031 Closes: https://github.com/gentoo/portage/pull/976 Signed-off-by: KARBOWSKI Piotr <slashbeast@gentoo.org> Signed-off-by: Mike Gilbert <floppym@gentoo.org>
* cnf: add arch-specific configuration example for loongWANG Xuerui2022-12-101-0/+56
| | | | | | | | | This is partially based on the riscv text. Bug: https://bugs.gentoo.org/884135 Signed-off-by: WANG Xuerui <xen0n@gentoo.org> Closes: https://github.com/gentoo/portage/pull/956 Signed-off-by: Sam James <sam@gentoo.org>
* cnf: sets: add @rust-rebuild setSam James2022-09-301-0/+6
| | | | | | | | | | | Rust is statically linked like Go and this is useful for us to mention in GLSAs (and possibly dev-lang/rust{,-bin}'s pkg_postinst). Bug: https://bugs.gentoo.org/827974 Bug: https://bugs.gentoo.org/865115 Signed-off-by: Sam James <sam@gentoo.org> Closes: https://github.com/gentoo/portage/pull/915 Signed-off-by: Sam James <sam@gentoo.org>
* cnf: sets: convert @golang-rebuild into VariableSetSam James2022-09-291-3/+3
| | | | | | | | | | | | | | | | | | | | | | | This allows rebuilding *all* Go packages correctly, rather than purely going off inherit. There's a few reasons to do this: 1. Even if (and it's a big if) we suppose that all Go packages should inherit a Go eclass, there will be packages in user repositories which don't do that; 2. Eclasses are, by their nature, repository-specific. This solution is a generic approach independent of the eclass layout in ::gentoo. Bug: https://bugs.gentoo.org/827974 Bug: https://bugs.gentoo.org/865115 Signed-off-by: Sam James <sam@gentoo.org> Closes: https://github.com/gentoo/portage/pull/898 Signed-off-by: Sam James <sam@gentoo.org>
* Scheduling policy switchingKARBOWSKI Piotr2022-08-031-0/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | Adds ability to control the scheduler policy that is used for emerge and all child processes. Mainly to interface the ability to switch to SCHED_IDLE as the solution to keep interactive tasks unaffected by building process happening in the background. On a test sample N=1 with AMD Ryzen 5950x and 64 GB of ram building sys-devel/gcc with lto enabled significantly reduces responsiveness of the system, even with CONFIG_SCHED_AUTOGROUP and PREEMPT enabled. Using a web browser result in visible lags, video playback in web browser, when using CPU decoding, also suffers greatly. Switching Portage to SCHED_IDLE (PORTAGE_SCHEDULING_POLICY="idle") results in no visible slowdowns and responsiveness is as if nothing in the background was happening. This is especially worthy feature when running on powerful CPUs, where users often opt in to build not only with parallel build jobs, but also with multiple packages at once. Anyone running with PORTAGE_NICENESS="19" will undoubtedly want to use this feature to force SCHED_IDLE policy. Closes: https://github.com/gentoo/portage/pull/861 Signed-off-by: KARBOWSKI Piotr <slashbeast@gentoo.org> Signed-off-by: Mike Gilbert <floppym@gentoo.org>
* *: use /usr/bin/env bash iso /bin/bashFabian Groffen2022-07-251-1/+1
| | | | | | | For Prefix systems it's better not to use host-provided bash (if it exists at all), and this is in line with python usage as well. Signed-off-by: Fabian Groffen <grobian@gentoo.org>
* repoman: RemoveMatt Turner2022-05-021-1/+1
| | | | | | | | RepoMan sez: So long and thanks for all the fish! I'll be enjoying my retirement now. Haven't I done enough to deserve that? Bug: https://bugs.gentoo.org/835013 Signed-off-by: Matt Turner <mattst88@gentoo.org>
* autoclean: only enable for global updates and depcleansSam James2022-04-131-1/+1
| | | | | | | Closes: https://bugs.gentoo.org/792195 Signed-off-by: Sam James <sam@gentoo.org> Closes: https://github.com/gentoo/portage/pull/795 Signed-off-by: Sam James <sam@gentoo.org>
* dispatch-conf: add a warning about changing the use-rcs settingMike Gilbert2022-04-111-0/+3
| | | | | | | | If there are existing files in the archive directory, this may cause conflicts with the files/directories managed using rcs. Bug: https://bugs.gentoo.org/837533 Signed-off-by: Mike Gilbert <floppym@gentoo.org>
* dispatch-conf.conf: frozen-files is space-separatedRobert Booth2022-02-061-1/+2
| | | | | Bug: https://bugs.gentoo.org/830618 Signed-off-by: Zac Medico <zmedico@gentoo.org>
* */*: GPKG (new binpkg format) Support (GLEP 78, provisionally)Rin Cat (鈴猫)2022-01-242-0/+57
| | | | | | | | | | | Bug: https://bugs.gentoo.org/500630 Bug: https://bugs.gentoo.org/659864 Bug: https://bugs.gentoo.org/672672 Bug: https://bugs.gentoo.org/773259 Bug: https://bugs.gentoo.org/820578 Signed-off-by: Rin Cat (鈴猫) <dev@rincat.ch> Closes: https://github.com/gentoo/portage/pull/562 Signed-off-by: Sam James <sam@gentoo.org>
* Exclude binary cache build for live ebuildsMadhu Priya Murugan2021-11-191-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit introduces a new value "buildpkg-live" for FEATURES, which is enabled by default (so the default behavior of building binary cache for all packages is retained). When it is disabled by calling emerge with FEATURES="-buildpkg-live", binary caches will not be built live ebuilds even if we specify --buildpkg. So that it is no longer necessary to pass a list of packages with live ebuilds to --buildpkg-exclude. Before this commit, when an emerge is called with the option '--buildpkg', a binary cache for the package is created under /var/cache/binpkgs. For example, when we do a, 'emerge --ask --verbose --buildpkg some-gitpkg/abc', a binary cache abc-1.1.1.tbz2 is created under /var/cache/binpkgs/some-gitpkg. With this commit, even if we explicitly use the options, '--buildpkg' for the packages with live ebuilds, no binary cache will be created (given we disable it calling emerge with FEATURES="-buildpkg-live"). Motivation: Since binary caches are created for all packages, including packages with live ebuilds, a separate list of (for eg.,) git packages needs to be maintained. And this is then passed to the options '--buildpkg-exclude' via, EMERGE_DEFAULT_OPTS. So the motivation behind this patch was to reduce redundancy, while we can simply disable binary cache for live ebuilds with this option. Closes: https://github.com/gentoo/portage/pull/766 Signed-off-by: Madhu Priya Murugan <madhu.murugan@rohde-schwarz.com> Signed-off-by: Zac Medico <zmedico@gentoo.org>
* Add make.conf.example for riscvMarek Szuba2021-11-161-0/+61
| | | | | Bug: https://bugs.gentoo.org/812434 Signed-off-by: Zac Medico <zmedico@gentoo.org>
* lib/portage/_sets/dbapi.py: add glob support to exclude-files parameter ↵Dave Hughes2021-05-231-0/+1
| | | | | | | | cnf/sets/portage.conf: add exclude-files=/usr/src/linux* in module-rebuild set Closes: https://github.com/gentoo/portage/pull/694 Signed-off-by: Dave Hughes <davidhughes205@gmail.com> Signed-off-by: Zac Medico <zmedico@gentoo.org>
* make.globals: default enable FEATURES=binpkg-multi-instanceZac Medico2021-02-221-0/+1
| | | | | Bug: https://bugs.gentoo.org/715112 Signed-off-by: Zac Medico <zmedico@gentoo.org>
* Add @changed-subslot package setMatt Turner2021-01-171-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This set is the upgradable packages for which the highest visible version has a different subslot than the currently installed version. The primary purpose of this feature is for use in catalyst builds. We update the "seed" stage3 before using it to build a new stage1. Updating the entire stage is expensive and unnecessary (since we're going to build the latest packages in stage1 and then rebuild everything in stage3). What we definitely do need to update in the original stage3 however, is any package that would trigger a subslot rebuild. For example: gcc links with libmpfr.so from dev-libs/mpfr. mpfr's SONAME changes from libmpfr.so.4 (SLOT="0/4") to libmpfr.so.6 (SLOT="0/6"). If the seed stage's dev-libs/mpfr is not updated before emerging gcc, gcc will link with libmpfr.so.4, but the latest version of dev-libs/mpfr will be built and libmpfr.so.6 included into the stage1. Since the old libmpfr.so.4 is not included in the stage1, gcc will not work, breaking subsequent stage builds. Our current options to update the seed are too large a hammer (e.g., "--update --deep --newuse @world" or "--update --deep --newuse --complete-graph --rebuild-if-new-ver gcc") and spend too much time updating seed stages for no gain beyond updating only packages for whom the subslot has changed. With this set, catalyst will likely use emerge @changed-subslot --ignore-built-slot-operator-deps y to update the seed stage. Thank you to Zac Medico for showing me how to do this. Bug: https://bugs.gentoo.org/739004 Signed-off-by: Matt Turner <mattst88@gentoo.org> Signed-off-by: Zac Medico <zmedico@gentoo.org>
* cnf/sets/portage.conf: add new sets for go rebuilding go packagesGeorgy Yakovlev2020-11-011-0/+6
| | | | | | | | | | | | | | | | | | | go-built binaries may contain security vulnerabilities if a binary built with vulnerable compiler. go is known to embed vulnerable code to all binaries it builds, if vulnerability was present in the compiler or one of standard libraries. This commit adds `golang-rebuild` set, which allows easy rebuild of most go-compiled system packages. simple 'emerge @golang-rebuild' should rebuild everything affected. a prompt to run this command can be added to postinst message in dev-lang/go ebuild. Closes: https://github.com/gentoo/portage/pull/630 Bug: https://bugs.gentoo.org/752153 Signed-off-by: Georgy Yakovlev <gyakovlev@gentoo.org> Signed-off-by: Zac Medico <zmedico@gentoo.org>
* cnf/repo.postsync.d/example: Detect metadata/pkg_desc_index in repoZac Medico2020-10-141-1/+2
| | | | | | | Detect when the repo includes a metadata/pkg_desc_index file and in that case skip the call to egencache --update-pkg-desc-index. Signed-off-by: Zac Medico <zmedico@gentoo.org>
* egencache: add --external-cache-only option (bug 737470)Zac Medico2020-09-131-10/+9
| | | | | | | | | | | | | The --external-cache-only option is useful for client-side use cases where writing cache files inside the repository itself may interfere with repository verification. This option is currently supported for --update and --update-pkg-desc-index actions, for which consumers of the corresponding cache or index files are already capable of consuming files from the external cache directory (/var/cache/edb/dep). Bug: https://bugs.gentoo.org/737470 Signed-off-by: Zac Medico <zmedico@gentoo.org>
* egencache --update-pkg-desc-index: emulate esync --verbose output (bug 737470)Zac Medico2020-09-071-1/+1
| | | | | | | | | | | | | | | | When the --verbose flag is given, make --update-pkg-desc-index emulate esync --verbose output. Example: * Searching for changes [ N] acct-group/ultimaker (0): Group for ultimaker [ N] acct-user/ultimaker (0): User for ultimaker [ U] www-client/opera (70.0.3728.144): A fast and secure web browser [MU] www-client/opera-developer (72.0.3798.0): A fast and secure web browser [ U] x11-libs/gtksourceview (4.6.1-r1): A text widget implementing syntax highlighting and other features Bug: https://bugs.gentoo.org/737470 Signed-off-by: Zac Medico <zmedico@gentoo.org>
* cnf/repo.postsync.d/example: add egencache --update-pkg-desc-index (bug 735626)Zac Medico2020-08-081-1/+14
| | | | | | | | | Add an egencache --update-pkg-desc-index example for users of app-portage/esearch to migrate to. Bug: https://bugs.gentoo.org/735626 Reviewed-by: Brian Dolbec <dolsen@gentoo.org> Signed-off-by: Zac Medico <zmedico@gentoo.org>
* Default BINPKG_COMPRESSION to zstd (bug 715108)Zac Medico2020-05-241-2/+3
| | | | | | | | | | | This includes a _compat_upgrade.binpkg_compression script that the ebuild can call in pkg_preinst in order to maintain a backward-compatible bzip2 default when appropriate, ensuring that binary package consumers are not caught off guard. Bug: https://bugs.gentoo.org/715108 Reviewed-by: Brian Dolbec <dolsen@gentoo.org> Signed-off-by: Zac Medico <zmedico@gentoo.org>
* make.globals: add default BINPKG_COMPRESS setting (bug 715108)Zac Medico2020-05-031-1/+4
| | | | | | | | | | The ebuild will have a default enabled USE=zstd which changes the default to zstd here. Bug: https://bugs.gentoo.org/715108 Bug: https://bugs.gentoo.org/719456 Reviewed-by: Brian Dolbec <dolsen@gentoo.org> Signed-off-by: Zac Medico <zmedico@gentoo.org>
* Support FEATURES=qa-unresolved-soname-deps (bug 708448)Zac Medico2020-02-081-1/+2
| | | | | | | | | | | | Support FEATURES=qa-unresolved-soname-deps so that it's possible to disable the QA warning that was introduced for bug 704320. This is useful for systems that may have incomplete PROVIDES metadata due to alternative package managers or experimentation with a new architecture. Bug: https://bugs.gentoo.org/708448 Bug: https://bugs.gentoo.org/704320 Signed-off-by: Zac Medico <zmedico@gentoo.org>
* make.globals: Change FETCHCOMMAND_RSYNC to --copy-linksMichał Górny2019-10-211-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | Change FETCHCOMMAND_RSYNC to use '-Lt' over '-a'. Notably, this replaces --links with --copy-links option, i.e. makes rsync copy underlying files when symlinks are met. This is important since we do not transfer symlink targets, therefore '-l' ends up creating dangling symlinks. This also removes most of the other options that are irrelevant or even undesirable to distfile fetching, that is: - '-r' since we always fetch a single file, so recursive operation is unnecessary - '-p', '-o', '-g' since we want to apply our permissions and ownership for distfiles rather than copying the one from mirrors, - '-D' since we do not expect any devices or specials in distfiles. Copying timestamps is preserved in case it's helpful in determining whether files need to be refetched. Bug: https://bugs.gentoo.org/698046 Reviewed-by: Zac Medico <zmedico@gentoo.org> Signed-off-by: Michał Górny <mgorny@gentoo.org>
* repos.conf: remove mention of squashdelta from default configBertrand Jacquin2019-09-251-4/+0
| | | | | | | | | squashdelta was removed in 090c8c91dad9 ("portage/sync/modules: Remove the squashdelta module") Bug: https://bugs.gentoo.org/614422 Closes: https://github.com/gentoo/portage/pull/461 Signed-off-by: Zac Medico <zmedico@gentoo.org>
* x11-module-rebuild: support SYMLINK_LIB=no (bug 693980)Zac Medico2019-09-111-1/+1
| | | | | | | Use a lib* glob to support SYMLINK_LIB=no. Bug: https://bugs.gentoo.org/693980 Signed-off-by: Zac Medico <zmedico@gentoo.org>
* Drop removed git and tla from list of live eclasses.Ulrich Müller2019-07-271-1/+1
| | | | Signed-off-by: Ulrich Müller <ulm@gentoo.org>
* Support PROPERTIES="live".Ulrich Müller2019-07-271-1/+7
| | | | | Bug: https://bugs.gentoo.org/233589 Signed-off-by: Ulrich Müller <ulm@gentoo.org>
* repos.conf: default sync-webrsync-verify-signatureZac Medico2019-07-101-0/+1
| | | | | | | | | | | | | | | | | | Enable sync-webrsync-verify-signature by default in repos.conf (due to dependencies the ebuild will make this conditional on USE=rsync-verify in the same way as the default sync-rsync-verify-metamanifest value). Use a new PORTAGE_TEMP_GPG_DIR variable to distinguish indirect emerge-webrsync calls that use gemato for secure key refresh, and disable direct emerge-webrsync calls. Deprecate FEATURES=webrsync-gpg and use it to trigger a backward-compatibility mode where direct emerge-webrsync calls are allowed (but trigger a warning message). Since direct emerge-webrsync calls do not use gemato for secure key refresh, this behavior will not be supported in a future release. Bug: https://bugs.gentoo.org/689506 Signed-off-by: Zac Medico <zmedico@gentoo.org>
* repos.conf: Default to using Gentoo keyserversMichał Górny2019-07-051-0/+1
| | | | | | | | | Default to using hkps://keys.gentoo.org which are guaranteed to hold the newest copies of Gentoo keys, are secured against key poisoning and are more reliable than SKS. Reviewed-by: Zac Medico <zmedico@gentoo.org> Signed-off-by: Michał Górny <mgorny@gentoo.org>
* Update default RPMDIR to /var/cache/rpm.Ulrich Müller2019-06-091-1/+1
| | | | | | | | | | After the other locations have been updated, RPMDIR is the only directory with a default under /usr/portage. Update its default along the lines of PKGDIR. Bug: https://bugs.gentoo.org/687734 Signed-off-by: Ulrich Müller <ulm@gentoo.org> Signed-off-by: Zac Medico <zmedico@gentoo.org>
* cnf/make.conf.example: remove comment about DISTDIR and PKGDIR in PORTDIRZac Medico2019-04-181-4/+1
| | | | | | Reported-by: Matt Whitlock <gentoo@mattwhitlock.name> Bug: https://bugs.gentoo.org/378603#c32 Signed-off-by: Zac Medico <zmedico@gentoo.org>
* Update /usr/portage references (bug 378603)Zac Medico2019-04-181-10/+6
| | | | | | | | | | Update all relevant references in docs, messages, and comments to refer to /var/db/repos/gentoo instead of /usr/portage. Also update DISTDIR and PKGDIR references to refer to the new /var/cache/{distfiles,binpkgs} locations. Bug: https://bugs.gentoo.org/378603 Signed-off-by: Zac Medico <zmedico@gentoo.org>