Re: F37 proposal: Build all JDKs in Fedora against in-tree libraries and with static stdc++lib (System-Wide Change proposal)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, May 11, 2022 at 10:37:31AM -0400, Omair Majid wrote:
> Hi,
> 
> Daniel P. Berrangé <berrange@xxxxxxxxxx> writes:
> 
> > One way to reduce this burden is to not introduce new JDKs to all
> > existing Fedora streams, only add it to rawhide so certification is
> > only needed once.
> >
> > Having said that I'm still not clear on the real impact of the
> > certification. Presumably thue certification is not re-done in each
> > JDK RPM re-build, nor on every RPM re-build of a library it depends
> > on.  If so, then do we really need to do certification for every
> > Fedora release stream when adding a new JDK. Can we do a build for
> > 35, certify it, and then do what is effectively no-change import
> > and rebuild for 36/37-rawhide and just consider the 35-certification
> > to cover those streams.
> 
> As I understand it, the certification (TCK) is only done on a binary
> level, and only applies to the OpenJDK package itself. It's not a
> one-time thing when a new version of the OpenJDK is added; it needs to
> be re-done on every single rebuild and/or update of OpenJDK.
> 
> AFAIK, even if you rebuild the exact same sources with the exact same
> toolchain with the exact same compiler flags, you still can't claim TCK
> certification status from one build carries over to the next.

With such a strict interpretation, then I would have thought that
any time a dependency got an update it would invalidate certification
too, even right down to any glibc update, or even kernel update ?

With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|
_______________________________________________
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




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux