On Thu, May 26, 2022 at 07:31:45PM +0200, drago01 wrote:
> I am not talking about FLOSS vs non FLOSS, that's obvious. But bundled libs
> and properly tested / certified vs dynamic linking and less testing / no
> certification.
I've been following this circular thread from the outset (And I do make
use of Fedora's JDK packages), but one thing I don't recall seeing is a
specific (or even general) example of the sort of failures/problems that
have come from linking against system libraries vs just using the
bundled ones.
Relatedly, I think it would also be very valuable to know if these
problems are mostly one-off (eg a major release of the jdk or dependent
library lands in rawhide and breakage ensues), or occur throughout a
specific release cycle (eg F35 gets libfoo 1.2.1 -> 1.2.2 for a critical
security update which leads to a failure to pass TCK, or quarterly
java-1.8.x -> 1.8.y update cycle leads to a TCK failure due to fedora's
bundled library libfoo version)
I mean, it's been strongly implied (if not outright stated) that
resolving these unspecified TCK failures, caused by using non-bundled
libraries, is the real burden, not the act of running the TCK for each
build -- but is the TCK (or upstream JDK) really that _brittle_?
- Solomon
--
Solomon Peachy pizza at shaftnet dot org (email&xmpp)
@pizza:shaftnet dot org (matrix)
High Springs, FL speachy (libra.chat)
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
