From owner-freebsd-ports@FreeBSD.ORG Wed Jun 25 18:13:32 2003 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 3902137B401 for ; Wed, 25 Jun 2003 18:13:32 -0700 (PDT) Received: from obsecurity.dyndns.org (adsl-64-169-104-32.dsl.lsan03.pacbell.net [64.169.104.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77A6D43FA3 for ; Wed, 25 Jun 2003 18:13:31 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id 81EFD66BE5; Wed, 25 Jun 2003 18:13:30 -0700 (PDT) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id 5BBF5AE6; Wed, 25 Jun 2003 18:13:30 -0700 (PDT) Date: Wed, 25 Jun 2003 18:13:30 -0700 From: Kris Kennaway To: Christian Weisgerber Message-ID: <20030626011330.GA38814@rot13.obsecurity.org> References: <20030625215041.GA37147@rot13.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="W/nzBZO5zC0uMSeA" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i cc: freebsd-ports@freebsd.org Subject: Re: Ports that don't run on !i386 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: Thu, 26 Jun 2003 01:13:32 -0000 --W/nzBZO5zC0uMSeA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jun 25, 2003 at 11:07:50PM +0000, Christian Weisgerber wrote: > Kris Kennaway wrote: >=20 > > .if ${ARCH} =3D=3D "alpha" > > BROKEN=3D"Does not compile on alpha" > > .endif > -snip- >=20 > I'm talking about ports that will successfully build but not *run*. > I.e. the program crashes on start-up or quickly thereafter. Obviously, > bento does not catch this. OK, then NOT_FOR_ARCHES is appropriate, since if it's just BROKEN then the package will still be created and distributed. Actually, one downside to using NOT_FOR_ARCHS is that you can't control the IGNORE message, so you can't explain the problem to the user. It might be a good idea to add a variable like IGNORE_MSG_ to allow people to document the nature of the problem on different architectures (there might be a cleaner way to do this without adding new variables). Also, as Mark pointed out, we probably need to make the IGNOREd ports more visible so that people stay aware of them. Kris --W/nzBZO5zC0uMSeA Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE++ki6Wry0BWjoQKURAlc2AJ0dIzaDkewNdKaKqOtYddMtdcKepACgs3GY 3HtGgceuSzBaUG1qKAUgGPk= =CTk4 -----END PGP SIGNATURE----- --W/nzBZO5zC0uMSeA--