Christian Lohmaier wrote: > Hi Terrence, *, > > On Mon, Jul 20, 2009 at 6:45 PM, Terrence Miller<[email protected]> > wrote: >> >> any source information needed to do a build should be in a source file and >> stored locally. > > No. That differs from system to system and thus cannot be stored in a > sensible way. > >> Examples of information that should be in a source files are: >> >> - A list of all the packages which need to be installed in order for the >> build to succeed. > > configure checks for that. If counfigure doesn't report any issues and > your build still doesn't succeed, then it is a bug in configure that > should be fixed.
I agree. Unfortunately not enough attention is paid to that - on a properly configured Linux system configure should run without parameters and without errors. > >> (better yet a script which will put a system in the desired state.) > > Again, see above. > >> - the options specified to configure > > Don't know what you're up to here. options are options for the reason > of being optionally turned on/off. So what sense does it make to > hardcode options? See above. As long as we can't guarantee that on most systems configure does not need any options to build OOo, we need to document that somehow. >> Also having any source files copied into external is (in my opinion) a >> problem. For example, >> the URL for gpc.[ch] could go dead overnight with no warning. > > gpc is no longer needed (for a looong time). Are you sure? You are right that OOo can be built without gpc (with the option to disable it), but no developer could tell me if that will create a loss of functionality or not. Kai Ahrens told me that he is going to make sure in 3.2 that gpc is no longer needed. Until then it's unclear to me wether we need it or not. Regards, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to "[email protected]". I use it for the OOo lists and only rarely read other mails sent to it. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
