Le 22/01/2018 à 23:28, Jan Engelhardt a écrit :
On Monday 2018-01-22 21:30, Hadrien Grasland wrote:
Le 22/01/2018 à 18:16, John Paul Adrian Glaubitz a écrit :
* Causes an ICE in that specific release of GCC, which was introduced by accident in what was supposed to be a simple bugfix. Very rare. So far I have only seen such problems on less common architectures and it was always a breeze to get these things fixed with upstream. It looks like you have enjoyed pretty well-written and unambitious C/++ code so far, then. Lucky you! Where I work, broken build systems, code and compilers are a relatively common sight, I'd say we deal with them every other month or so, and that is with a package base is much smaller than the repos of SuSE or Debian! Are you working in academia/science? There's quite a bit of bad code coming out of that field. But, a distribution is comprised of less than 20% (number pulled out of thin air) packages from obs://science, so indeed we don't experience as many WPM[1] as you may be ;-)
You're right, it's probably that :) My largest package management experience comes from HEP experiments, where we try to run quite poorly written and bleeding edge (C++14/17) software on very... ahem... *stable* RedHat releases, and it doesn't end very well. We basically end up maintaining everything but the kernel and libc ourselves in order to get sufficiently recent compilers and libs. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org