Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.java > #10113
| From | 殷啟聰 | Kai-Chung Yan <seamlikok@gmail.com> |
|---|---|
| Newsgroups | linux.debian.maint.java |
| Subject | Re: OpenJFX 9 integration |
| Date | 2017-10-24 09:10 +0200 |
| Message-ID | <uE1vz-8ee-3@gated-at.bofh.it> (permalink) |
| References | <uzUji-3ov-407@gated-at.bofh.it> <uDmsq-6XZ-1@gated-at.bofh.it> <uDxxv-674-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
Why not keep the source package name as "openjfx" and then name the binary package "openjdk-9-jfx"? Emmanuel Bourg 於 2017年10月23日 07:00 寫道: > Le 22/10/2017 à 12:57, Matthias Klose a écrit : > >> Are you aware if upstream is aware of these issues, and if they intend to stop >> using internal OpenJDK APIs? Any plans to get rid off the single file approach >> for the database files? > I don't know. At least they are aware that OpenJFX fails to build with a > raw OpenJDK not including OpenJFX and they seem willing to address that > issue. > > >> (C) looks like the best workaround for now. Looking at at least four security >> releases per year, and maybe the double amount of package uploads, the OpenJDK >> package has a higher upload frequency anyway. There is however a risk that an >> OpenJDK (security) update won't build anymore with a prebuilt OpenJFX (not sure >> if that is a real issue). In any case, the OpenJDK package should have a build >> profile to build without OpenJFX support. > Ok let's do that. The name of the package is open to discussion, as well > as how the OpenJFX files will be distributed between the openjdk-9-* > packages. > > For the name, since OpenJFX is now clearly becoming an extension of > OpenJDK I was thinking about naming the source package > "openjdk-9-openjfx" or "openjdk-9-jfx", and appending "-build" to the > binary package. What would be a good location for installing the build > directory? > > Regarding the distribution of the files, the lib/modules file of > openjdk-9-jre-headless will now contain the JavaFX classes, but the > native libraries should go into openjdk-9-jre. javapackager and > ant-javafx.jar would go into openjdk-9-jdk-headless. > > Emmanuel Bourg >
Back to linux.debian.maint.java | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
OpenJFX 9 integration Emmanuel Bourg <ebourg@apache.org> - 2017-10-13 00:40 +0200
Re: OpenJFX 9 integration 殷啟聰 | Kai-Chung Yan <seamlikok@gmail.com> - 2017-10-17 17:20 +0200
Re: OpenJFX 9 integration Emmanuel Bourg <ebourg@apache.org> - 2017-10-17 21:20 +0200
Re: OpenJFX 9 integration Matthias Klose <doko@debian.org> - 2017-10-22 13:20 +0200
Re: OpenJFX 9 integration 殷啟聰 | Kai-Chung Yan <seamlikok@gmail.com> - 2017-10-22 17:30 +0200
Re: OpenJFX 9 integration Markus Koschany <apo@debian.org> - 2017-10-22 21:00 +0200
Re: OpenJFX 9 integration Mykola Nikishov <mn@mn.com.ua> - 2017-10-22 23:00 +0200
Re: OpenJFX 9 integration Markus Koschany <apo@debian.org> - 2017-10-22 23:10 +0200
Re: OpenJFX 9 integration Emmanuel Bourg <ebourg@apache.org> - 2017-10-23 01:10 +0200
Re: OpenJFX 9 integration 殷啟聰 | Kai-Chung Yan <seamlikok@gmail.com> - 2017-10-24 09:10 +0200
Re: OpenJFX 9 integration Emmanuel Bourg <ebourg@apache.org> - 2017-10-24 12:20 +0200
Re: OpenJFX 9 integration Sebastiaan Couwenberg <sebastic@xs4all.nl> - 2018-04-04 07:20 +0200
Re: OpenJFX 9 integration Matthias Klose <doko@debian.org> - 2018-04-04 10:00 +0200
Re: OpenJFX 9 integration Emmanuel Bourg <ebourg@apache.org> - 2018-04-04 10:30 +0200
Re: OpenJFX 9 integration Bas Couwenberg <sebastic@xs4all.nl> - 2018-04-04 11:20 +0200
Re: OpenJFX 9 integration tony mancill <tmancill@debian.org> - 2018-04-04 15:50 +0200
Re: OpenJFX 9 integration Markus Koschany <apo@debian.org> - 2018-04-04 16:10 +0200
Re: OpenJFX 9 integration David Goodenough <david.goodenough@linkchoose.co.uk> - 2017-10-24 07:40 +0200
csiph-web