On Mon, Mar 21, 2005 at 03:09:26PM +0100, Andreas Barth wrote: > * Wouter Verhelst (firstname.lastname@example.org) [050321 15:05]: > > On Sun, Mar 20, 2005 at 03:16:08PM +0100, Andreas Barth wrote: > > > Well, the toolchain is perhaps not the part where they turn up most > > > likely, but it's the part that creates most of the workload and delays. > > > Uh. Most porting bugs that require attention fall in one of the > > following areas: > > * Toolchain problems (Internal Compiler Errors, mostly) > > * Mistakes made by the packager. Quite easy to fix, usually. > > * Incorrect assumptions in the source code. These are becoming > > increasingly rare these days, IME. > > Exactly. And if you s/workload/workload for the release team/, than the > first one is the usual spot for issues for us. The middle one is fixed No. Because you can always consider to leave the package out for that specific architecture (except if it would be a really important one). That would be far more acceptable then throwing out the complete archive for that architecture, that would be 'het kind weggooien met het badwater'. Cheers, Peter (p2).
Description: Digital signature