[Bug 453264] Review Request: jscoverage - A tool that measures code coverage for JavaScript programs
bugzilla at redhat.com
bugzilla at redhat.com
Sun Jun 29 18:51:24 UTC 2008
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
Summary: Review Request: jscoverage - A tool that measures code coverage for JavaScript programs
https://bugzilla.redhat.com/show_bug.cgi?id=453264
------- Additional Comments From jkeating at redhat.com 2008-06-29 14:51 EST -------
message from upstream (that I will later put in the spec file itself):
From: Ed <ed at siliconforks.com>
To: Jesse Keating <jkeating at redhat.com>
Subject: Re: Packaging jscoverage for Fedora
Date: Sun, 29 Jun 2008 12:01:38 -0500 (13:01 EDT)
Jesse Keating wrote:
> Hrm, that exposes a different problem. Fedora has a pretty strict
> policy with regard to statically compiled software, in that you have to
> have a really really good reason to bring it in and have the exception
> on file. Are there any ways to compile jscoverage against the shared js
> library?
>
The Mozilla SpiderMonkey js library is intended to be used as a
JavaScript interpreter, but JSCoverage uses it for parsing, rather than
interpreting, JavaScript. Unfortunately the parsing functions are not
"public" and could possibly change any time the library is upgraded.
I think the above qualifies as a good reason to allow static linking. I'm ready
to have this package reviewed.
The only current rpmlint output is a number of .css files in the examples have
dos line endings, which doesn't effect their use. If not necessary I'd rather
not munge those files during package build.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
More information about the Fedora-package-review
mailing list