Hello Stefano! > Is that not a decision for those porters to make? What's the > disadvantage of letting it continue to try to build there?
Exactly, it should be up to the porters whether we want a particular package to build on a certain target architecture or not and the package maintainer should not interfere with that unless there is an actual reason (e.g. the built package would be in any way harmful or problematic). > It seems fairly harmless, to me. After installing the build-deps the > package realises there isn't enough RAM, and aborts, wasting only a > few minutes of buildd time. Depending on the target architecture, installing the build dependencies of a package together with the preceding run of "apt-get update" can take a considerable amount of the time share of the total build time, so it does actually harm in a sense by wasting build time, yes. Please let the decision whether a certain package should be built on a certain architecture up to the porters. They (we) are in a much better decision to decide that and if we actually don't want a package to be built at all on a certain architecture, we just set it to "Not-For-Us" in the wanna-build database on the buildd master. There is no need for a package maintainer to influence that. Thanks, Adrian Porter for m68k and sh4 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - [email protected] `. `' Freie Universitaet Berlin - [email protected] `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
