Bug 977119 - Consider splitting /usr/bin/js and libmozjs to separate subpackages
Summary: Consider splitting /usr/bin/js and libmozjs to separate subpackages
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: js
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Pavel Alexeev
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-23 16:51 UTC by Kalev Lember
Modified: 2013-06-24 20:29 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-06-24 19:55:42 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 958426 0 unspecified CLOSED 19 Final TC1 x86_64 Desktop Live is oversized (larger than 1 GB) 2021-02-22 00:41:40 UTC

Internal Links: 958426

Description Kalev Lember 2013-06-23 16:51:04 UTC
We are over size with the F19 Desktop media and looking for ways to make cuts.

I've noticed that the /usr/bin/js executable is rather large (3.4 MB) and that contributes to the size of the iso image.

During the new mozjs17 package review (https://bugzilla.redhat.com/show_bug.cgi?id=948345) we came to a conclusion that there's nothing in Fedora that would make use of the /usr/bin/js17 interpreter at this point. The mozjs17 package now explicitly removes it: http://pkgs.fedoraproject.org/cgit/mozjs17.git/tree/mozjs17.spec#n67

Might be worth removing /usr/bin/js from this package as well, or perhaps move it to a subpackage.

Comment 1 Kalev Lember 2013-06-23 16:59:34 UTC
On a second look, there is plowshare that uses /usr/bin/js, but all other users that my repoquery finds seem to be only linking to the shared library.

Not sure how safe it would be to move /usr/bin/js to a separate subpackage at this point though, the F19 release is really close.

Comment 2 Adam Williamson 2013-06-23 17:28:49 UTC
Yeah, it'd be good if we can find space in other ways, and save this as a last resort.

Comment 3 Pavel Alexeev 2013-06-23 18:31:28 UTC
>During the new mozjs17 package review (https://bugzilla.redhat.com/show_bug.cgi?id=948345) we came to a conclusion that there's nothing in Fedora that would make >use of the /usr/bin/js17 interpreter at this point. The mozjs17 package now >explicitly removes it: >http://pkgs.fedoraproject.org/cgit/mozjs17.git/tree/mozjs17.spec#n67
Strange decision. I want suggest contra - split js17 in separate package for dependencies like plowshare and other scripting aims and then completely retire js package. It is quite old and I really does not understand why mozjs17 rereviewed instead of just update and replace js with name and provides.

Comment 4 Pavel Alexeev 2013-06-23 18:32:16 UTC
It then allow us to economy even more space.

Comment 5 Kalev Lember 2013-06-23 18:40:47 UTC
Yes, I believe that's the plan -- port all apps over to mozjs17 and then retire js. And I'm sure /usr/bin/js17 can be brought back now that we know there's a user (plowshare).

Comment 6 Kalev Lember 2013-06-23 19:03:00 UTC
Coming back to the original topic of splitting up 'js', the following might make sense:

 'js' package: /usr/bin/js
 'js-libs' package: libmozjs185.so.1.0

That way existing /usr/bin/js users (plowshare) don't need any modifications (Requires: js will still keeping pulling in the interpreter) and the library users will automatically switch over to the 'js-libs' subpackage through library deps.

That is, of course, if we feel it's safe enough to do for F19. It doesn't really matter much for F20 because most users are getting ported to mozjs17.

Comment 7 Kalev Lember 2013-06-24 19:55:42 UTC
Looks like the live media is finally under the size target, so this fix won't be needed for F19.

https://bugzilla.redhat.com/show_bug.cgi?id=958426#c42

Comment 8 Pavel Alexeev 2013-06-24 20:29:18 UTC
I do not argue to splitting, but think it have no many worth when we want retire it completely.

Please contact me in the future if I could help you something.


Note You need to log in before you can comment on or make changes to this bug.