Date: Tue, 1 Feb 2005 02:04:31 +0300 From: Roman Bogorodskiy <bogorodskiy@gmail.com> To: Danny Pansters <danny@ricin.com> Cc: freebsd-ports@freebsd.org Subject: Re: How to deal with an arch you don't have access to (pointyhat) Message-ID: <20050131230431.GA28556@lame.novel.ru> In-Reply-To: <200501312351.12611.danny@ricin.com> References: <200501312351.12611.danny@ricin.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050131230431.GA28556>