From: Ben Collins <[EMAIL PROTECTED]> Date: Mon, 23 May 2005 20:21:57 -0400
> But (and this but is for David), that means users can't simply do > "apt-get source foo; cd foo-1.1; dpkg-buildpackage" and get the same build > they got from us, which is a consistency Debian needs. Maintainers trying > to fix bugs on sparc in their packages that log in to one of our machines > shouldn't have to worry about this subtlety either. Make the login environment be sparc32 by default. Doesn't that solve the problem? And for die-hard 64-bit people like me they can undo this via some configuration mechanism. It is one option. Another option is to bite the bullet and think about real sub-arch'ing for debian packages. Then, for a *.sparc package the dpkg building knows to "sparc32 whatever", yet for a *.sparc64 package the dpkg building machinery does not. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
