From owner-freebsd-ports@FreeBSD.ORG Mon Jan 31 23:02:17 2005 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 C6BE716A4CF for ; Mon, 31 Jan 2005 23:02:17 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4302943D2D for ; Mon, 31 Jan 2005 23:02:15 +0000 (GMT) (envelope-from bogorodskiy@gmail.com) Received: by rproxy.gmail.com with SMTP id i8so108736rne for ; Mon, 31 Jan 2005 15:02:14 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:cc:subject:message-id:mail-followup-to:references:mime-version:content-type:content-disposition:in-reply-to:x-gpg; b=BhXQY1JtubTaVAoX8hk3xJbJFWtrwIu9tpAC+7gQQmApZIhF5PrT2YhAUo7YlybhP1WUxYcaVRe4eo1cYZPV8dYDX6Duh2GI9HG5TzSDDlbBptijPpYwZWh+PGfF1e0fQ8wU8oKo8VJa+A7Xt4d8P3CXpev6Mr8C8rTEZut/rbk= Received: by 10.38.97.67 with SMTP id u67mr115208rnb; Mon, 31 Jan 2005 15:02:14 -0800 (PST) Received: from localhost ([217.23.66.46]) by smtp.gmail.com with ESMTP id 70sm328799rnb.2005.01.31.15.02.05; Mon, 31 Jan 2005 15:02:14 -0800 (PST) Date: Tue, 1 Feb 2005 02:04:31 +0300 From: Roman Bogorodskiy To: Danny Pansters Message-ID: <20050131230431.GA28556@lame.novel.ru> Mail-Followup-To: Danny Pansters , freebsd-ports@freebsd.org References: <200501312351.12611.danny@ricin.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="VbJkn9YxBvnuCH5J" Content-Disposition: inline In-Reply-To: <200501312351.12611.danny@ricin.com> X-GPG: http://bmp-plugins.berlios.de/key cc: freebsd-ports@freebsd.org Subject: Re: How to deal with an arch you don't have access to (pointyhat) 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: Mon, 31 Jan 2005 23:02:18 -0000 --VbJkn9YxBvnuCH5J Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Danny wrote: > A port I maintain doesn't build on alpha 4. I have a possible solution (m= ight=20 > need to repeat for other modules that may have the same problem), but sin= ce I=20 > only have i386 myself I can't test it. I would think this is not an uncom= mon=20 > situation and so I wanted to ask how do port maintainers deal with this? >=20 > Of course I can PR, then wait and see how pointyhat does, then perhaps PR= =20 > again, etc. Doable but not very efficient, and I'm uncomfortable submitti= ng=20 > stuff that isn't tested in any way. So, what do people normally do in suc= h=20 > cases, try and find a guinea pig? As for me, I don't know any solution of this problem. Anyway, usually error logs give enough information to fix the problem. You can also ask somebody of commiters to help you with testing.=20 64 bit archs are still my headache though... -Roman Bogorodskiy --VbJkn9YxBvnuCH5J Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iQCVAwUBQf65f4B0WzgdqspGAQKIYQQAg4J4YG6C3whtG852FNy/ZukHQ3I5+MRl hitYnD94CWn4lcOZPcEShpZOx8N7SwyuP/Tt5gsJ0KIxOVmHj+6u4KOgcb9gxe8v 6niXIYhb1ZU0guE2rv9dGht+2e9+QI/ZEZpqbg7RwZB5sdFZ7+dKNqbCyZNDtILY Bcuh8tLWHSg= =+jRd -----END PGP SIGNATURE----- --VbJkn9YxBvnuCH5J--