From owner-freebsd-ports@FreeBSD.ORG Thu May 4 16:57:28 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 7D7CB16A401 for ; Thu, 4 May 2006 16:57:28 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3532A43D45 for ; Thu, 4 May 2006 16:57:28 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 1F2BB1A4D82 for ; Thu, 4 May 2006 09:57:28 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 6853A51589; Thu, 4 May 2006 12:57:27 -0400 (EDT) Date: Thu, 4 May 2006 12:57:27 -0400 From: Kris Kennaway To: freebsd-ports@freebsd.org Message-ID: <20060504165727.GA67780@xor.obsecurity.org> References: <44538D42.8030301@chrismaness.com> <200605010901.50654.aren.tyr@gawab.com> <20060501091523.GA38820@pentarou.parodius.com> <200605021827.34873.aren.tyr@gawab.com> <20060504094155.GC984@roadrunner.q.local> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+QahgC5+KEYLbs62" Content-Disposition: inline In-Reply-To: <20060504094155.GC984@roadrunner.q.local> User-Agent: Mutt/1.4.2.1i 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: Thu, 04 May 2006 16:57:28 -0000 --+QahgC5+KEYLbs62 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 04, 2006 at 11:41:55AM +0200, Ulrich Spoerlein wrote: > Aren Olvalde Tyr wrote: > > Perhaps it would be good, if, say on the corresponding port entry on th= e=20 > > FreeBSD ports webpage, it listed all the options used for building the = binary=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 opt= ions=20 > > used, with the package download link at the bottom. Or something like t= hat.=20 > >=20 > > Just an idea. What do people think?=20 >=20 > I'd even go further. This is something I have been thinking about on and > off. Namely, a FLAVOUR system for packages. A maintainer specifies up to > three FLAVOURs per port, which set various flags for building the port. In FreeBSD land these are called "slave ports", and you can have as many as you like. I don't have any interest in adding a separate "flavour" system in parallel to this. Kris --+QahgC5+KEYLbs62 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEWjJ2Wry0BWjoQKURAjoEAKChAPyu8aQpp8tdkgPtE4m5f79qXgCfeK8P CPrlm3xQwiY3cfKFhLYAkwI= =2yrN -----END PGP SIGNATURE----- --+QahgC5+KEYLbs62--