831341 – java-utils-2.eclass: ensure dev-java/java-dep-check is pulled

Bug 831341 - java-utils-2.eclass: ensure dev-java/java-dep-check is pulled

Summary: java-utils-2.eclass: ensure dev-java/java-dep-check is pulled

Status:	CONFIRMED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Eclasses (show other bugs)
Hardware:	All Linux

Importance:	Normal normal (vote)
Assignee:	Java team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2022-01-17 08:49 UTC by Pacho Ramos
Modified:	2022-01-18 17:22 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Pacho Ramos gentoo-dev

2022-01-17 08:49:58 UTC

I was wondering why I was getting this log message in all my systems upon updating of pdftk package:
Install dev-java/java-dep-check for dependency checking

I then saw it comes from java-utils-2_pkg_preinst in java-utils-2.eclass and I wondered why I need to manually emerge that package instead of getting it automatically pulled as BDEPEND as it seems to be needed 

Thanks

Comment 1 Yuan Liao (Leo3418) 2022-01-18 07:47:53 UTC

dev-java/java-dep-check inherits java-pkg-2.eclass, making it an indirect descendant of java-utils-2.eclass.  If we put BDEPEND="dev-java/java-dep-check" into java-utils-2.eclass, it would effectively be added into dev-java/java-dep-check too, creating a package that unconditionally depends on itself.  Therefore, this is not feasible.

Anyway, the dependency check is just an optional check enabled by setting the JAVA_PKG_STRICT variable.  Setting or unsetting JAVA_PKG_STRICT does not make any difference in terms of functionality and correctness of the build artifacts.

Comment 2 Sam James archtester

2022-01-18 10:04:05 UTC

(We could actually add an exemption for that package.)