commit: 1fa044467282982563c2cf42c9918b8f4d03d58b Author: Matt Turner <mattst88 <AT> gentoo <DOT> org> AuthorDate: Thu May 14 02:10:40 2020 +0000 Commit: Matt Turner <mattst88 <AT> gentoo <DOT> org> CommitDate: Fri May 15 00:53:50 2020 +0000 URL: https://gitweb.gentoo.org/proj/catalyst.git/commit/?id=1fa04446
doc: Drop pre-EAPI-5 text There are very few EAPI < 5 ebuilds left. Signed-off-by: Matt Turner <mattst88 <AT> gentoo.org> doc/catalyst-config.5.txt | 30 +----------------------------- 1 file changed, 1 insertion(+), 29 deletions(-) diff --git a/doc/catalyst-config.5.txt b/doc/catalyst-config.5.txt index 4fe1af8c..f17944b2 100644 --- a/doc/catalyst-config.5.txt +++ b/doc/catalyst-config.5.txt @@ -168,22 +168,7 @@ This section is only important if you are using binary packages to build your stages (by enabling the `pkgcache` option and restarting incomplete builds). -Before EAPI-5 introduced ABI sub-slots, the build-time compatibility -of packages was not recorded. This leads to problems such as binary -GCC packages built against mpc-0.8.2 (which installs libmpc.so.2) -being installed on systems that only have mpc-1.0.1 (which installs -libmpc.so.3), resulting in: - ---------------------------------- -/usr/libexec/gcc/i686-pc-linux-gnu/4.6.3/cc1: - error while loading shared libraries: libmpc.so.2: - cannot open shared object file: No such file or directory ---------------------------------- - -As long as there are packages in your stage that don't use ABI -sub-slots, you may experience errors like this due to untracked ABI -missmatches in binary packages. Packages generated by catalyst builds -are currently namespaced: +Packages generated by catalyst builds are namespaced: If versioned_cache is set: --------------------------------- @@ -194,19 +179,6 @@ Otherwise: .../packages/<rel_type>/<target>-<subarch>/Packages --------------------------------- -so running into these out-of-date packages is unlikely. You may run -into problems if: - -* you enable `update_seed` in your stage1 spec after a previous run - which generated packages linking against out-of-date seed libraries - or -* you update your snapshot and an untracked ABI dependency is bumped - without a similar bump in the dependent package. - -without also bumping any of the package namespace variables in your -spec. If you do make such a change, it's a good idea to clear the -package cache in question and rebuild the packages from scratch. - FILES -----
