1 |
On Fri, 27 Jul 2012 22:56:27 -0700 |
2 |
Bryan Gardiner <bog@××××××.net> wrote: |
3 |
|
4 |
> On Thu, 26 Jul 2012 18:22:10 +0400 |
5 |
> Евгений Пермяков <permeakra@×××××.com> wrote: |
6 |
> |
7 |
> > Can someone tell me, why my gentoo server wants X header to build |
8 |
> > icedtea jdk if USE="... -X ..." ? Ok, I understand that it is |
9 |
> > because maintainers wrote ebuild that requires X header |
10 |
> > unquestionable. But why they did so and can be something done about |
11 |
> > it? Do not want to have *-bin* package in system for perfectionism |
12 |
> > reasons. |
13 |
> |
14 |
> Hi, |
15 |
> |
16 |
> If it helps, it looks like dev-java/icedtea with USE=-X only requires |
17 |
> X to build, not to run. So after installation, the X packages can be |
18 |
> removed by "emerge --ask --depclean --with-bdeps=n packages...". Or |
19 |
> leave off "packages..." to see all installed packages that are not |
20 |
> needed for world packages to run (which should include X). |
21 |
> |
22 |
> Of course you'll have to reinstall them if you want to rebuild |
23 |
> icedtea... |
24 |
|
25 |
Speaking somewhat generically: |
26 |
|
27 |
Turns out this is fairly common in the real world. Huge numbers of java |
28 |
apps have some form of config utility and most of them are (sadly) not |
29 |
headless. They are gui-driven and that's the only way they can be |
30 |
configured. We sysadmins don't like this, but there's not much we can |
31 |
do about it. |
32 |
|
33 |
So we compromise. It's fairly normal to install Xlibs on a box running |
34 |
java and export the display. This appears to be what the |
35 |
icedtea maintainers settled on. |
36 |
|
37 |
At least the maintainers used their brain and require Xlibs, not a full |
38 |
blown running X server. |
39 |
|
40 |
|
41 |
-- |
42 |
Alan McKinnon |
43 |
alan.mckinnon@×××××.com |