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

Bug#676784: Policy §10.5 and .jar file noticeable exception



On Wed, Jul 24, 2013 at 05:06:50PM +0300, Eugene Zhukov wrote:
> On Wed, Jul 24, 2013 at 4:41 PM, Charles Plessy <plessy@debian.org> wrote:
> > Le Wed, Jul 24, 2013 at 03:55:38PM +0300, Eugene Zhukov a écrit :
> >>
> >> I encountered a Lintian warning executable-not-elf-or-script with one
> >> of my packages and then I learned about outstanding
> >> Lintian<->debian-policy bug #539315.
> >>
> >> How about fixing the policy by adding an exception for .jar files?
> >
> > Dear Eugene,
> >
> > I do not see where the Policy forbids JAR files to be executable when they are
> > intended to be executed.  In line with others, I think that the interpretation
> > of section 10.5 on symbolic links in #539315 is overly restrictive, as
> > executable JAR files are not just compressed files, but entire archives.
> >
> > Altogether, I think that we should close #676784 (the clone of #539315), or
> > clarify what is the intent of section 10.5, and what is meant by "compressed"
> > there.
> 
> The problem with section 10.5 is in the clause "A symbolic link
> pointing to a compressed file should always have the same file
> extension as the referenced file".
> So, if I have /usr/share/java/foo.jar, then I want to have executable
> foo in /usr/bin through link foo -> ../share/java/foo.jar. Which is
> now, as I see it, against the policy.

No really: a compressed file is expected to have an extension like .gz, .bz2, .xz or .zip etc.
The policy is helpful because various tools will not uncompress such files if they do not
have the right extensions.

A .jar file is not a compressed file in the sense it is not meant to be uncompressed
with unzip or zless etc.

Cheers,
-- 
Bill. <ballombe@debian.org>

Imagine a large red swirl here. 


Reply to: