Closed Bug 59110 Opened 25 years ago Closed 25 years ago

win32 nightlies contain both jar and uncompressed chrome

Categories

(SeaMonkey :: Build Config, defect, P3)

x86
Windows 98
defect

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 53462

People

(Reporter: bugZ, Assigned: cls)

Details

For some time now, all the chrome and skins have been in jar files, but the win32 nightlies (other than installer.exe) still contain both jars and all the uncompressed chrome/skins - almost 2.5M worth of excess. The uncompressed files are no longer needed to run Mozilla, so please remove them from the nightly zip files. If somebody actually wants uncompressed files, they can always extract them from the jar files. Those of us with slow connections will appreciate it.
--> build config I asked the same question once, and was told that it was there for debug purposes. If you have a slow connection you should get the installer however, letting build config people choose what to do with this. Adding leaf to cc cause he loves spam and is our main build person
Assignee: asa → cls
Status: UNCONFIRMED → NEW
Component: Browser-General → Build Config
Ever confirmed: true
QA Contact: doronr → granrose
See also the discussion in bug 53462 "Option for jars only in tarballs". Adding that bug as dependency. Is a separate bug needed for linux, or is the linux case covered by these two existing bugs? BTW, if the uncompressed chrome is removed from the tarballs, we might want to include an "unjar" utility in the chrome dir that takes care of the extra directory level when the jars are unzipped. I have made something for unix here: http://bugzilla.mozilla.org/showattachment.cgi?attach_id=18213 This makes unzipping the chrome as simple as "cd chrome && unjar *.jar" Maybe someone can come up with something similar for Windows? I strongly agree that the uncompressed chrome should be removed from the tarballs, especially given that it's trivial to recreate it if desired.
Depends on: 53462
*** This bug has been marked as a duplicate of 53462 ***
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
No longer depends on: 53462
must of missed it somehow, verified
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.