Re: Policy change proposal, Re: Bug#176628: sablevm: package incorrctly provides java1-runtime
> This is where I stand right now with at least one package: I cannot
> depend on java1-runtime because two of the three packages that provide
> it *don't work*. By leaving the java1-runtime tag on the incomplete
> VM packages, I'm required to maunally validate these packages
> continuously or simply ignore their existence. IMHO, neither of those
> alternatives is effective.
Sure, and the java-awt-runtime / java-swing-runtime or whatever proposal
(i.e., virtual packages that refer specifically to GUI toolkits) will
resolve your problem AFAICT.
I realise it's not pretty pulling out a specific subset of the java
specs and turning them into separate virtual packages, but in this case
I'd argue it's warranted since AFAIK the GUI toolkits are particular
sticking points with free JVMs.
b.
Reply to: