Features/Thunderbird/Improved Build System: Difference between revisions

Features/Thunderbird/Improved Build System (view source)

540 bytes added , 6 July 2012

no edit summary

canmove, Confirmed users, Bureaucrats and Sysops emeriti

3,628

edits

@@ Line 12: / Line 12: @@
 Due to the build system not being an exact copy, there are high porting and maintenance overheads to keep up to date with mozilla-central. These need to be reduced.
+As well as the build system, there are improvements to the packaging system to be made to help ensure Thunderbird is shipping with the correct files.
 |Feature users and use cases=Developers and building of Thunderbird.
-|Feature implementation plan=There's several possible stages:
+|Feature implementation plan=For the build-config part, there's several possible stages:
 ) In comm-central, prototype the extraction of Thunderbird and Mailnews specific arguments into a sub-configure file that is called from the configure file, but is as minimal as possible and does not duplicate the build system into the sub-configure ({{bug|648980}})
@@ Line 22: / Line 24: @@
 ) Assuming that's not viable, investigate fully switching comm-central to be a sub-directory under mozilla-central ({{bug|648979}})
+Also, for packaging system, there's a couple of bugs worth trying to fix:
+- {{Bug|713133}} This will make package failures fatal, so if we're trying to package things that no longer exist, we'll get warned about it.
+- {{Bug|526333}} Defines a core package-manifest for all apps to use and share, which helps with reducing breakages when core items are added.
 }}
 {{FeatureInfo