commit: 6c0b51ae63833c2ddfd58412727c0004db06d605 Author: Joonas Niilola <juippis <AT> gentoo <DOT> org> AuthorDate: Sat Apr 23 12:42:10 2022 +0000 Commit: Joonas Niilola <juippis <AT> gentoo <DOT> org> CommitDate: Sun May 22 06:37:02 2022 +0000 URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=6c0b51ae
general-concepts/dependencies: expand on finding correct deps a bit Signed-off-by: Joonas Niilola <juippis <AT> gentoo.org> Closes: https://github.com/gentoo/devmanual/pull/284 general-concepts/dependencies/text.xml | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-) diff --git a/general-concepts/dependencies/text.xml b/general-concepts/dependencies/text.xml index ab1a799..59b1b37 100644 --- a/general-concepts/dependencies/text.xml +++ b/general-concepts/dependencies/text.xml @@ -631,7 +631,9 @@ package: <dd> Use a tool like <c>scanelf -n</c> (from app-misc/pax-utils) or <c>objdump -p</c> (from sys-devel/binutils) to list <c>DT_NEEDED</c> - entries + entries. + app-portage/iwdevtools and portage's own <c>qa-unresolved-soname-deps</c> + <b>FEATURE</b> can help finding these. </dd> <dt>Look in <c>configure.ac</c></dt> <dd> @@ -647,12 +649,12 @@ package: <dt>Look at the application/library website</dt> <dd> Check the application website for possible dependencies that they suggest - are needed + are needed. </dd> <dt>Read the <c>README</c> and <c>INSTALL</c> for the package</dt> <dd> They usually also contain useful information about building and installing - packages + packages. </dd> <dt> Remember non-binary dependencies such as pkg-config, doc generation @@ -664,6 +666,12 @@ package: are clearly stated. Again, such dependencies usually belong in <c>BDEPEND</c>. </dd> + <dt>Testing in chroots, containers and virtual machines</dt> + <dd> + A sure-way to find missing dependencies is to test your ebuild in a + deprived environment. Chroots, containers, virtual machines and + dev-util/ebuildtester can achieve this. + </dd> </dl> </body>
