Closed
Bug 58376
Opened 24 years ago
Closed 22 years ago
End-user vs maintainer builds
Categories
(SeaMonkey :: Build Config, defect, P3)
SeaMonkey
Build Config
Tracking
(Not tracked)
VERIFIED
WONTFIX
Future
People
(Reporter: cls, Assigned: cls)
References
Details
As we move closer to an end-user product (meaning working browser and components to be used by non-mozilla developers), we need to cut down on the amount of cruft that we compile/install. Since someone will inevitably claim that some of this cruft actually means something for mozilla developers, I propose adding an --enable-maintainer-build switch or something that will set the necessary flags to build the additional programs wanted by mozilla developers. The problem with adding yet another switch is that you can end up with bustage seen by with the option but not without and vice-versa. To that end, we may want to consider adding a 'make check' phase, which actually builds the extra "test" programs and runs them to make sure that they work. Or you could replace the current test programs with a real regression suite.
Updated•23 years ago
|
Keywords: mozilla1.0
Updated•23 years ago
|
Keywords: mozilla1.0+
Updated•23 years ago
|
Keywords: mozilla1.0
Comment 1•22 years ago
|
||
As far as I can see, this would cut off a lot of bloat for the nightly builds. Yay!
Updated•22 years ago
|
Target Milestone: mozilla1.0 → Future
Comment 2•22 years ago
|
||
Wishful thinking.
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → WONTFIX
Comment 3•22 years ago
|
||
<http://www.beonex.com/communicator/version/0.8/source>
Comment 4•22 years ago
|
||
Rather <http://www.developer.beonex.com>. (sorry for spam)
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•