| 1 |
On Thursday, February 2, 2017 10:36:51 AM EST Michael Orlitzky wrote: |
| 2 |
> Why does dev-java/icedtea try to pull in GTK (and thus X) |
| 3 |
> on a headless server? That stuff belongs in a desktop profile, not in |
| 4 |
> the base one. |
| 5 |
|
| 6 |
In that specific case it cannot be avoided. Building is not the same as using. |
| 7 |
Even if you are not using aspects, they still need to be built. Even a |
| 8 |
headless server may do graphics manipulation, image, video, etc. Thus will |
| 9 |
require graphical type libraries to build those portions of Java. |
| 10 |
|
| 11 |
Building something is not the same as using the result. You have the same |
| 12 |
issues with -bins, oracle, and icedtea. The difference is its pre-built. You |
| 13 |
would only run into issues if you tried to use a portion of Java that relied |
| 14 |
on system libraries not present. Thus those have use flags that will pull in |
| 15 |
additional libraries like javafx, etc. |
| 16 |
|
| 17 |
People with this dream of building java from source do not really understand |
| 18 |
what all it takes. Building Java on a servers is not ideal as you will need X |
| 19 |
libraries, etc. To truly do it from source, you have to bootstrap back to 1.5, |
| 20 |
and build each version in succession. Or use a pre-build binary from a prior |
| 21 |
version to build current, icedted-7 (1.7) to build ~icedtea-3 (1.8). |
| 22 |
Versioning is another matter and topic. |
| 23 |
|
| 24 |
Java is moving to a more modular build and deployment system. Starting with |
| 25 |
Java 9. Maybe in the future pieces can be built and a headless server version |
| 26 |
would not require X to build from source. Though given graphical library usage |
| 27 |
previously mentioned. Some parts may always bring in things you may not want |
| 28 |
on a server. |
| 29 |
|
| 30 |
-- |
| 31 |
William L. Thomson Jr. |
Archives