Terrence Miller <terrencem <at> sbcglobal.net> writes: > I am about half way through my first build Hi Terrence,
thank you for taking the time to report back. > and have already run into things > which could lead to unstable Linux builds: My experience has convinced > me that > any source information needed to do a build should be in a source file > and stored locally. Well, for some stuff, that is not possible for legal reasons (licenses etc.). > 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. OpenOffice can be build almost selfcontained with almost no external dependencies. The deps start to get interesting when you use the --with-system-XXXX switch and use distro-provided packages. However, when reproducable builds are the aim (as are for our RelEngs), you wouldnt be using anything external, but use the library versions from the OOo repo. So the information is "in the source files": The reference version of a library is the one found in the OOo repo. > (better yet a script which will put a system in the desired state.) > - the options specified to configure Thats a package maintainer task (as package maintainers might want to compile against patched libs, or enable/disable features). > 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. Right, this is why this dep will be completely removed for 3.2. > If OOo wants to be able to reproduce builds, we will need to have a > local snapshot of any package listed as a build requirement. Where possible those are already in the OOo repo. Thanks for your comments and enjoy hacking OOo! Best Regards, Bjoern Michaelsen --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
