If jar packaging is enabled, the individual files are still copied to dist/bin. Consequently, they are also packaged. This is a space waste for normal users. Workaround: Manually eelete the dirs under dist/bin/chrome before packaging for distribution. Would be nicer, if we had a flag not to copy them there in the first place. RFE: Add it.
Ben: I don't think the process works like you think. We copy the files to dist _in order to_ zip them up. We could delete them after zipping, but I don't really see why that's necessary, and it could lead to other problems. Besides, the "normal users" you're talking about aren't really normal -- they're early adopters who take tarballs complete with test programs and all sorts of extra cruft. I'd say this is pretty low priority.
> We copy the files to dist _in order to_ zip them up. Oh, ic. Then my suggestion is to add the option to delete them shortly before packaing, in xpinstall/package/Makefile.in et al.. warren, how do I best get the list of packages from within a Makefile? > Besides, the "normal users" you're talking about aren't really normal No, I was speaking about really normal users - users of a Mozilla distributions. This bug would make creating such a distribution a bit easier.
The build team didn't want to tweak anything put into dist by the build process before zipping up. They don't want to introduce more complexity and potential problems. Normal users are ones who take our beta bits, with installers, etc. People taking tarballs are already signed up for giving up at least a gigabyte of disk space. What's a few meg more more between friends?
> Normal users are ones who take our beta bits, with installers, etc. There is not only Netscape. This bug is about making life easier for competitors of Netscape. That's the whole purpose of mozilla.org, not? What problem could it cause to remove left-overs from the build process in the dist dir of an BUILD_OFFICIAL build tree?
isn't this a dup of bug 53462?
yes. *** This bug has been marked as a duplicate of 53462 ***
Status: NEW → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.