From owner-freebsd-ports@FreeBSD.ORG Tue May 2 17:27:41 2006 Return-Path: X-Original-To: freebsd-ports@freebsd.org 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 5538A16A406 for ; Tue, 2 May 2006 17:27:41 +0000 (UTC) (envelope-from aren.tyr@gawab.com) Received: from info10.gawab.com (info10.gawab.com [204.97.230.43]) by mx1.FreeBSD.org (Postfix) with SMTP id E621443D48 for ; Tue, 2 May 2006 17:27:40 +0000 (GMT) (envelope-from aren.tyr@gawab.com) Received: (qmail 14615 invoked by uid 1004); 2 May 2006 17:29:47 -0000 Received: from unknown (HELO yggdrasil) (aren.tyr@gawab.com@212.225.32.38) by gawab.com with SMTP; 2 May 2006 17:29:47 -0000 X-Trusted: Whitelisted From: Aren Olvalde Tyr To: freebsd-ports@freebsd.org Date: Tue, 2 May 2006 18:27:26 +0100 User-Agent: KMail/1.9.1 References: <44538D42.8030301@chrismaness.com> <200605010901.50654.aren.tyr@gawab.com> <20060501091523.GA38820@pentarou.parodius.com> In-Reply-To: <20060501091523.GA38820@pentarou.parodius.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart573296278.dQ1nnClntQ"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200605021827.34873.aren.tyr@gawab.com> Subject: Re: Upgrade Tool X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 17:27:41 -0000 --nextPart573296278.dQ1nnClntQ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 01 May 2006 10:15, Jeremy Chadwick wrote: > Because using binary packages much nullifies any port Makefile knobs > that're used for compile or configure-time purposes. You're stuck using > whatever defaults the person who built the binary package used. Good point.=20 On the subject of which, does anyone know if there is any convention for th= e=20 pre-built FreeBSD packages? i.e. Are they built extremely conservatively,=20 with all optional bits switched off, or aggressively, i.e. all optional bit= s=20 on? Or is it "default", i.e. most commonly wanted options on, more obscure= =20 off; or finally, just purely random, down to whatever the person who built= =20 the package happened to choose at the time depending on their mood? > I've never "fully trusted" binary packages (I do for some ports, not for > others) due to not knowing what options someone has built them with... Perhaps it would be good, if, say on the corresponding port entry on the=20 =46reeBSD ports webpage, it listed all the options used for building the bi= nary=20 package. For example, for the "Package" link, instead of simply linking to= =20 the package, it could link to a page entry listing all of the build options= =20 used, with the package download link at the bottom. Or something like that.= =20 Just an idea. What do people think?=20 Aren. --nextPart573296278.dQ1nnClntQ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQBEV5aGoWGxb6IQ4B4RAn/FAKCiRP+X82yvPxuUroZFa6o5A71xsgCfWa6V +/NvDrRpHreQPwrXdO79CG0= =SDEl -----END PGP SIGNATURE----- --nextPart573296278.dQ1nnClntQ--