From owner-freebsd-ports@FreeBSD.ORG Sun Jun 20 04:47:00 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2BBE816A4CE for ; Sun, 20 Jun 2004 04:47:00 +0000 (GMT) Received: from dragon.roe.ch (line-zh-102-185.adsl.econophone.ch [212.53.102.185]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7EB1843D2D for ; Sun, 20 Jun 2004 04:46:59 +0000 (GMT) (envelope-from daniel@roe.ch) Received: from roe by dragon.roe.ch with LOCAL id 1BbuEB-0006PK-00 for ports@FreeBSD.org; Sun, 20 Jun 2004 06:46:47 +0200 Date: Sun, 20 Jun 2004 06:46:47 +0200 From: Daniel Roethlisberger To: ports@FreeBSD.org Message-ID: <20040620044647.GA24274@dragon.roe.ch> Mail-Followup-To: ports@FreeBSD.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="n8g4imXOkfNTN/H1" Content-Disposition: inline User-Agent: Mutt/1.5.4i Subject: Testing ports/patches on non-i386 (such as amd64) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Jun 2004 04:47:00 -0000 --n8g4imXOkfNTN/H1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I maintain a port (mail/libspf) which currently does not compile on amd64, and probably on some other tier 1 or 2 architectures too. I am fairly optimistic that I will be able to cook up some patches to remedy this; however, I have no way of actually testing these on said architectures, as I currently do not have access to any non-i386 FreeBSD systems. What's the best way to handle such a situation as port maintainer? Should I file a PR asking for a committer to test my patches? Or should I find someone able and willing to do some testing for me through other means, such as posting patches to this list? Or should I just go ahead and have the untested patches committed, and wait for the bento logs to tell me about success or failure? (I don't particularly like this one). Any other options? Cheers, Dan --=20 Daniel Roethlisberger GnuPG key ID 0x804A06B1 (DSA/ElGamal) --n8g4imXOkfNTN/H1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQFA1Ra3OXQOmIBKBrERAto4AJ92STMwDbfkhxXgj3fKA47MJsPkxACdFlDN Lm+bHMRmXOfS3/E6QNzlbj4= =v+H+ -----END PGP SIGNATURE----- --n8g4imXOkfNTN/H1--