Jyri Virkki wrote: > This is another reason to move away from the obsolete consolidation > concept though. If the source to an individual component is not > individually available, there's no practical way to make this work. >
And this technique is of course antithetical to the concept of reproducible builds for system components, or for a set of components that all change over time. Core operating system components must be built using consolidations; these components are rev'd together and are expected to be deployed together. For ancillary components such as Apache or various leaf packages, defining a single build environment against which each individual package is built makes sense, and is realizable. But this technique forestalls the adoption of new interfaces as they become available. For the dev releases of OpenSolaris, consolidations make perfect sense and greatly reduce the difficulty of larger scale changes. Such an build system would also mean that the developer wishing to reproduce a component needs to very carefully construct his compilation environment. - Bart -- Bart Smaalders Solaris Kernel Performance [email protected] http://blogs.sun.com/barts "You will contribute more with mercurial than with thunderbird." _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
