On Thu, 2010-12-16 at 09:28 -0700, Kevin Fenzi wrote: > On Thu, 16 Dec 2010 10:03:30 -0600 > Chris Adams <cmadams@xxxxxxxxxx> wrote: > > > Once upon a time, Stanislav Ochotnicky <sochotnicky@xxxxxxxxxx> said: > > > Note that I am not saying things should go into buildroot as soon as > > > they are built, but as soon as they are in updates-testing. There > > > is a difference. There will still be reasons to use tags/overrides. > > > > That makes the push process much more fragile/difficult. If you use a > > updates-testing build of package A, and package B (that depends on > > package A) gets rebuilt, then you may have a package B that can't be > > pushed to stable until package A gets pushed. What if there's a > > security update on package B that needs to go to stable ASAP? > > Additionally, what if package A is built, after a few days serious > problems are found in it and it's deleted until the maintainer can sort > them out. What happens to packages B, C, D, and E that built against > this version? They will have broken deps. > > I don't think this is worth even looking at until we have an AutoQA > broken dep test live. There may even be cases in which B won't have a broken dep and still won't work with the previous version of A (or at all). All packages that were built against the new A may have to be tracked down and rebuilt, like with GCC bug 634757, which becomes a PITA. -- Matt -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
