"Rob C" <[EMAIL PROTECTED]>: > On 19/04/07, Christian Faulhammer <[EMAIL PROTECTED]> wrote: > > Steve Long <[EMAIL PROTECTED]>: > > > On the issue of QA, I think enabling FEATURES="collision-detect" > > > by default would do a lot more good at this stage than "test". > > Arch teams normally have collision-protect enabled when doing > > keywording/stabling....in my eyes this is sufficient. > Its obviously not, Many users are reporting file-collisions on a > weekly basis. So either this isn't sufficient or the arch teams are > not acting as you describe.
I can only speak for x86 team where it is mandatory for arch testers and devs. As far as I can tell other architecture teams handle it the same. Jakub already pointed out that many have very minimal chroots for stabling, while my chroot is cluttered with 1500 packages which should detect a lot of collisions. Just out of interest: How many file-collisions are filed per-week? V-Li
signature.asc
Description: PGP signature
