Re: F27 Self Contained Change: Decouple system java setting from java command setting

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2017-06-20 20:07, nicolas.mailhot@xxxxxxxxxxx wrote:
Hi,

Frankly, the proposed change seems a great way to accumulate technical debt at a rapid pace, by helping apps to specify various legacy or proprietary Java variants, and postponing taking into account openjdk changes indefinitely.

Why do you think so? The proposal doesn't say anything like that. It doesn't let apps specify their Java. The setting for Java applications will still be global.

Moreover, Fedora doesn't ship legacy or proprietary Java variants.


That's more or less what the proprietary unixes did till the whole house of cards collapsed under the weight of long overdue migration needs.

IIRC the whole alternative system already lets an app specify a specific java version and producer (at least it did in JPackage time). What it does not let people do is to pretend an app is java-version and java-producer agnostic when it isn't.

%jpackage_script generated launcher scripts don't let an app specify java version/provider and that will stay the same.

Michael
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux