> On Feb 6, 2023, at 12:03 PM, Henning Heinold > <henn...@itconsulting-heinold.de> wrote: > > Am Sun, Feb 05, 2023 at 10:52:59AM -0800 schrieb Robert Joslyn: >> Sorry, forgot to add Richard L to CC when sending the patch! >> >> Robert >> > > Thanks for your work, but I am bit torn here, because > one goal of oe was that all packages can be compiled > by its own, so we can link against different sets of > libc implementations and not repackaging some binary stuff. > But in the end I would go with the decision of Richard Leitner.
I agree, I would certainly prefer to build from source. I even run Gentoo so I can build from source on my workstation. But I have only a small need for Java and don’t have the time to get a newer Java building from source in OE (nor an employer willing to pay for it). Since getting it building is non-trivial, and we’re moving away from Java anyway, the easy answer is to grab some trusted binaries and use them until we hopefully migrate fully away from Java. Posting this to the list is mostly to share the work in the hope it’s useful to others in the same position. Ideally those more invested in Java would spend the time to write proper recipes. > >> On Feb 5 2023, at 9:34 am, Robert Joslyn >> <robert.jos...@redrectangle.org> wrote: >> >>> +++ b/recipes-core/temurin/temurin.inc >>> @@ -0,0 +1,62 @@ >>> +HOMEPAGE = "https://adoptium.net"; >>> +LICENSE = "GPL-2.0-with-classpath-exception" > > There are a lot more licenses involved according to: > https://projects.eclipse.org/projects/adoptium.temurin Hmm, I was going based on the NOTICE file in the tatrball which says, This program and the accompanying materials are made available under the terms of the GNU General Public License, version 2, with the Classpath Exception. Additional information relating to the program and accompanying materials license and usage is available as follows. * For Eclipse Temurin version 8 see the LICENSE and ASSEMBLY_EXCEPTION files in the top level directory of the installation. * For Eclipse Temurin version 9 or later see the files under the legal/ directory in the top level directory of the installation. SPDX-License-Identifier: GPL-2.0 WITH Classpath-exception-2.0 The legal directory in the tarball does have a LICENSE file for each library, but every one is a symlink to the same GPL-2.0 license file with a classpath exception. Maybe the other licenses are used for things that aren’t distributed as part of the binaries? I could update the recipes to checksum the other LICENSE files to make sure they don’t change (there are 70 of them in the JDK and 50 in the JRE). Thanks for the review! Robert
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#100953): https://lists.openembedded.org/g/openembedded-devel/message/100953 Mute This Topic: https://lists.openembedded.org/mt/96765795/21656 Group Owner: openembedded-devel+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
