Closed Bug 58376 Opened 24 years ago Closed 22 years ago

End-user vs maintainer builds

Categories

(SeaMonkey :: Build Config, defect, P3)

defect

Tracking

(Not tracked)

VERIFIED WONTFIX
Future

People

(Reporter: cls, Assigned: cls)

References

Details

Blocks: 58372
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.
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9
Target Milestone: mozilla0.9 → mozilla1.0
Keywords: mozilla1.0+
Keywords: mozilla1.0
As far as I can see, this would cut off a lot of bloat for the nightly builds. Yay!
Target Milestone: mozilla1.0 → Future
Wishful thinking.
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → WONTFIX
Rather <http://www.developer.beonex.com>. (sorry for spam)
verified
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.