On Sat, 29 Nov 2008 13:37:48 +0100 Laurent Guignard <lguignard.debian@gmail.com> wrote: > I have another question about architecture : > How is it possible to check if a package could be built on > architecture without the appropriate hardware ? As long as all the dependencies exist on all the available architectures and as long as the package itself does not insist on a particular architecture in the ./configure, then the package will need to build on all architectures. If it does not, that is a FTBFS bug. The only time to exclude particular architectures for a particular package is if the package has no possible role on such architectures or relies on dependencies that have no possible role. If a package relies on particular hardware that is only available for certain architectures, that would be a reason to only specify those architectures. Without such limitations, all packages must build on all architectures supported by Debian - failure to fix those bugs is likely to result in the removal of the package from Debian. What you can do is make sure that the package build is as portable as possible by using things like 'make distcheck' and ensuring that it always completes. You can try and build the package on whatever hardware you can access - a good range would be i386, amd64 and powerpc. Most of that hardware is relatively easy to obtain or request access. > I can say that dhcp-probe could be build on i386 and any compatible > architectures and with the upstream notes, i can say that dhcp-probe > could be built on sparc but how to test on other architectures ? It has to build on sparc, you are required to ensure that it does by fixing any FTBFS bugs that appear and those will provide a lot of the information you need to fix the bug. In that case, your sponsor can help you test the package on the actual hardware. -- Neil Williams ============= http://www.data-freedom.org/ http://www.linux.codehelp.co.uk/ http://e-mail.is-not-s.ms/
Attachment:
pgpUsPVWK_HtF.pgp
Description: PGP signature