https://bugzilla.redhat.com/show_bug.cgi?id=725733
Zbigniew Jędrzejewski-Szmek <zbyszek(a)in.waw.pl> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|fedora-review? |fedora-review+
--- Comment #5 from Zbigniew Jędrzejewski-Szmek <zbyszek(a)in.waw.pl> ---
(In reply to Vít Ondruch from comment #3)
* How to best use the CC.
Another option would be to stay closer to upstream and use the
"java -jar" call, but that fails with "Closure::Error: no main
manifest
attribute, in /usr/share/java/closure-compiler/closure-compiler.jar"
error
and I was told that this is not supported way how to execute Java stuff
on Fedora. So any opinion in this matter?
IIUC, specifying the main class in
the manifest onlly works if jar is
self-contained
and has all the dependencies, or if the classpath is specified through some
other
means. But could add the manifest, but I don't think that would be useful.
- Originally, the cc.jar was included in library. I remove it and
patch the
library quite extensively to use %{_bindir}/closure-compiler instead.
Nevertheless, the far simpler approach would be to replace the .jar file
by symlink, but that would mean that the filename will not correctly
reflect the actual version of CC neither the internal constant would be
correct.
Dunno. I'd say that whatever works... is good enough.
* Best way to require CC.
- So far, I used BR: closure-compiler but I might change it to
BR: %{_bindir}/closure-compiler, since that is the executable used
in the end.
Yeah, for BR either is OK. For R using the path would be annoying
because
the file list would have to downloaded.
Wouldn't it be easier to use the tarball from github for everything, and ignore
the gem? Hm, I see that the guidelines say that the released gem *must* be
used. Too bad.
+ license is specified OK
+ license file is present
+ sources match the license
+ %license macro is used
+ package name is OK
+ Guidelines:Ruby are followed (I'm not an ruby expert though)
+ package owns all directories except for /usr/share/gems and
/usr/share/gems/doc, but those are owned by rubygems
+ cc was unbundled
+ fs layout is OK
+ spec file is legible
- subpackage -doc bundles Lato fonts and jquery... See below.
+ latest version is packaged
+ %check is present and passes
+ %gem_install is used
+ rpmlint:
rubygem-closure-compiler.noarch: W: no-documentation
rubygem-closure-compiler.src: W: invalid-url Source1:
closure-compiler-1.1.11-tests.tgz
3 packages and 0 specfiles checked; 0 errors, 2 warnings.
The only issue seems to be the bundling of Lato and jquery. But that seems to
be completely standard in rubygems. So please just add Provides:
bundled(jquery). At some point we should unbundle jquery from everything, but
most likely it's better to do it in some automated fashion instead of manually
in every package.
Package is APPROVED.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component