On Thursday 29 May 2008 07:11:41 Pascal Bleser wrote: [snip]
Well personally, I don't see the point of "always building". It's JVM bytecode. It's portable. No point in building (except to make sure it compiles and runs with JDK 1.4 if 1.4 is all you have and you don't trust upstream saying it runs with 1.4).
Hi, the source code is really necessary for a future maintenance - patching of the appliaction distributed as jar(s) file(s) is possible, but it is a hell! I understand, that for BuildService only it is not important, because there's no maintenance - maintaner could update to newest version, if its necessary. But that package is unusable for openSUSE and vill not be included to the distribution. Yes, there may be some packages, which are in binary form only, but this is a historicall reason. We preffer to replace them by normall source based packages. So, the packaging of jars is possible, but is not really regular and peoples *have* to know it. The python packages also contains the source (py) and a bytecode (pyc/pyo) files. I know, that in the Java upstream is using of the jars regular and using of the source codes and building the own jars not, so its a harder way, but the only possible for the openSUSE and other Linux distributions. [snip]
None, besides using the macro instead of the environment variable. Just a matter of taste on this one.
One advantage of using macros instead of enviroment variables is, that the macros are expanded in the scripplets (%post/%pre/...), but the environment variables not. So an output of the rpm -q --scripts will be different. Best Regards Michal Vyskocil -- To unsubscribe, e-mail: opensuse-java+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-java+help@opensuse.org