On Sat Jun 09 12:08, Niels Thykier wrote: > There are is also Policy ยง10.5: > > """ > A symbolic link pointing to a compressed file should always have the > same file extension as the referenced file. (For example, if a file > foo.gz is referenced by a symbolic link, the filename of the link has to > end with ".gz" too, as in bar.gz.) > """ > > Jar files are zip files, so it should most likely be considered a > compressed file. I notice that (e.g.) sat4j "violates this" and uses > /usr/bin/sat4j to point to a jar file in /usr/share/java (with a .jar > extension).
I don't want to disagree with Niels' point about binfmt-misc, but I do think the fact that jar files are zip files here is coincidental. People are not meant to interact with them as zip files, they are meant to load them as Java libraries or programs. Using zip (and not elf, or something else) as the packaging format is an implementation detail. If executable jars via binfmt-misc is allowed then they certainly should be on the path without a .jar extension - users should invoke them without any need to know they are written in Java. Matt
signature.asc
Description: Digital signature
