Assumption 1: When ON starts producing IPS packages out of the build bfu
will be obsolete (In my opinion if it isn't then IPS needs enhancements
until it does obsolete bfu).
Assumption 2: We will continue to need cross consolidation flag day
coordination.
Assumption 3: Other consolidations will move to producing IPS packages
around the same time as ON does.
Given the above I'd like to recommend that the practice of "update
scripts" that grab stuff from other consolidations be highly discouraged
or actually disallowed as a way of dealing with build related flag days.
The rationale for this is that we want to people to actually use 'pkg
image-update' to update their build/test systems rather than the
"hackery" that sometimes has to go on today. This should mean that we
can keep public and private build machines on the bleeding edge much
more easily.
A build flag day that requires updates on the build machine that is just
for ON could be dealt with by having an ON 'nightly' IPS repository.
That ON 'nightly' repository needs updates from the closed and open
sides of ON. It could also contain a special 'closed-bins.tar' package
as well to help those that can't or don't want to access the onnv-closed
Mercurial source repository.
However the situation is much harder with cross consolidation flag days,
and this is the case were "update scripts" often come into play. I
think this implies that either all consolidations that ON has build
dependencies from also need a nightly IPS repository or we need a
central nightly IPS repository that all consolidations deliver into.
I'm sure other consolidations have similar build related issues but
since I don't often deliver to them I don't notice them. Hence the
reason for discussing this on on-disc...@. Note that pkg-discuss@ is
cc'd for the initial heads up but please respect the Reply-To: header.
--
Darren J Moffat
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
