On 12/7/15 7:27 PM, Rich Freeman wrote: > On Mon, Dec 7, 2015 at 7:05 PM, Alec Warner <[email protected]> wrote: >> 2) Unclear ownership of the problem. One guy makes a commit, 100 packages >> break. Who is responsible? Its really murky. This is really the toughest >> problem to me. > It isn't murky at all. Nobody should ever commit something that > simply breaks something else. Sometimes it is unforseen, and that > might be ok if it is rare, but the committer can still go and revert > their commit and sort things out.
Does that include stuff that breaks on systems using musl instead of glibc? Or uclibc? or eudev instead of udev. What about openrc vs systemd? Shall I go on? Of course its murky. If you disagree, I'll be more than happy to pull out dozens of emails where people object when their stuff breaks other people's stuff with the infamous "why should we support that shit?" Anyhow, if the emails are easily filter or have an easy out, I see no problem. Murky or not. -- Anthony G. Basile, Ph.D. Gentoo Linux Developer [Hardened] E-Mail : [email protected] GnuPG FP : 1FED FAD9 D82C 52A5 3BAB DC79 9384 FA6E F52D 4BBA GnuPG ID : F52D4BBA
