On Sun, Sep 30, 2018 at 06:22:23PM +0300, Adrian Bunk wrote: > Noone is talking about no longer supporting running Debian on > single-core systems.
Well, you are talking about dropping (or lowering) support for building Debian on single-core systems. But we are not a proprietary software company where what you call "using" is the "usual thing" and building is a "special thing", secondary in importance, that it is only guaranteed to work in the official buildds. We are a free software project, and being able to build the package is essential to what we offer. There is no excuse to take away this essential freedom just because "it builds ok in the buildds", the same way there would not be an excuse to ship packages that do not work just because "they work in the buildds". Just becase less people try the packages by building them does not mean that building is less important than "using" them. So I'll ask again: Why do you want to deprecate building on single-core and not "using" in single-core? If we followed your "real-world" arguments, support for both things should be on par. > Building all packages on the baseline is never possible, and I already > tried to explain to you that your "1 CPU with unlimited RAM" scenario is > pretty far away from the real-world problems. This is double standards again. Not being able to build all packages on the baseline has never been an excuse to not submit baseline violations (when we find them) as serious. You do that, and I fully support it, but for some strange reason assumming multi-core is "ok to the point of downgrading this bug" while assuming, say, SSE on i386, is not. Please explain that. Thanks.
