Petr Sumbera wrote:
> You might want to discuss with Mike whether it's not possible to install
> new Apache packages before putback itself. Building SFW is far too way
> from perfect.
So is everything in this world :) but feel free to try fixing it.
> This way you wouldn't have to do so many patching and you
> could build against installed Apache on system.
>
> I believe it's better to fix somehow SFW building procedure then patch
> programs in gate in the way they become "unreadable".
In general, requiring new packages to be installed on the build machine
before people can build your bits, particularly when it's packages built
from the bits you putback, is not good. It forces everyone who maintains
a build machine to upgrade to your bits before they can merge with the
gate and continue on their work, which theoretically can be quite
a few people these days. It can also be a pain if your bits turn
out to be broken and have to be backed out, or if we have to do a respin
of some previous bits but they need the old package and the nightly
build needs the new one. Some of that can be avoided by keeping you out
if we think there may be respins, or by buying hardware with money we
don't have, or setting up zones with ip's we don't have, but it's still
a concern :)
That said how much patching are we doing here? If it's a ton there
certainly are possibilities:
1. require your new package to be installed before the build. That's
a coordination problem with the gatekeepers for the gate builds, then
annoyance for build machine maintainers and others as they stumble on
build failures because they didn't see your flag day about this
(since it seems most flag days are indeed ignored until they hit you
in the face :)
2. include your patches for now, then remove them in a few builds once
it's reasonable to assume everybody has upgraded. according to the
CBE you're supposed to be building N on no later than N-2 (so build
77 on no later than 75), and though that's not always true it's
probably a reasonable start.
Mike
