Hi, > If the code is going to exist in the repo then we need to do better at > actually making sure it builds, and so I might make the controversial > suggestion that, so long as i386 kernel sources exist in main and are > supported in at least one stable branch, we should have at least one kernel > config that’s part of the default universe build, so we actually test the > code rather than finding out it’s broken when a user reports it or it gets > MFCed. This state of affairs doesn’t save effort, it just defers it, and if > anything makes it worse because people have to diagnose the error, rather > than it just be fixed from the start by the original author.
As a person who fixed several i386 compilation errors by others, I completely agree. This is common sense, and I don't see how that could be controversial. Some people are loosing time because of this, and overall it makes the process more inefficient than it could be. If for some reason re-integrating it in universe builds is not sustainable, then that simply means it's time to let go of i386. Regards. -- Olivier Certner
signature.asc
Description: This is a digitally signed message part.
