I'm not that headstrong. If doing that fake package I propose will provoke other problems, then of course, don't do it. I can not be a judge of that, you people are the experts.
I'm not an expert; I just happen to know a bit of Oracle packaging ways because I've gone through a situation very close to yours. In my case, it was inside of a corporate environment where the stuff is only to be used on our own deployments, so we can afford to do nasty stuff... openSUSE is different. openSUSE offers a JVM implementation (openJDK), which is very nice and pumps quite an impressive performance (you can test this easilly with Jenkins against the Oracle JVM's - grin -). That's what we support! We support it because we have access to the sources and we build it ourselves. Furthermore, from a JNI point of view, applications should still be compatible. As far as I am aware, Oracle is still the biggest contributor for the JNI code base. It's not openSUSE fault that Oracle decided that no one else could redistribute their JVM implementation; if you want to use it, you gotta run according to their rules... And their rules are quite easy... install the bloody thing and use 'alternatives'. If it's not friendly with zypper, you gotta ring Oracle bells, not ours... Only them can change it. We can't introduce mechanisms that will bring hellish situation to users for the sake of software we can't support... It's nothing technical about it, it's legal and good sense :) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org