:-( Something needs to be done about this. I've asked for control over the alpha distro myself, but didn't get a response. Either it's too complicated, requires too many priviledges or they want to remain in control, which makes the process slow, in-efficient and definately not scaleable.
Alpha, i586 and src.rpm get mirrorred to my machine every hour, the build script builds what hasn't been built before (or hasn't been rebuilt in the last XX days). Then the sync script uploads the packages missing in the alpha port. Circle complete. For me the distro in Paris is leading.
Circle is complete for me too. There's not a darn thing I can do about obsolete binary rpms in Paris, so I don't even try anymore. I download latest source, build/upload. What happens after that is out of my hands.
Yeah... but only you have access to your repository, and at the end of the day, that one isn't exposed to the outside world. The paris one is. If you are making the ISO's that go into the product, then in effect the people on the cooker-ppc list are testing the wrong product, although the differences aren't hat big.I'm sure not going to mirror all that obsolete crap back here. I've already cleaned up my own repository.
I rebuild them to check if they still rebuild. Quite often something changes in the distro which has impact on other parts. I see that quite quickly. It's an automated process, so it doesn't matter. It does, however, rely heavily on correct dependancies.I don't rebuild things just because they haven't been rebuilt in a while, as the upload will be rejected anyway. We all waste enough cycles as it is with 2+ releases of KDE/day lately.
Stefan
smime.p7s
Description: S/MIME Cryptographic Signature
