From owner-freebsd-ports@FreeBSD.ORG Fri Feb 2 22:24:57 2007 Return-Path: X-Original-To: ports@FreeBSD.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 356BC16A405; Fri, 2 Feb 2007 22:24:57 +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 2073A13C4A3; Fri, 2 Feb 2007 22:24:57 +0000 (UTC) (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 463151A4D81; Fri, 2 Feb 2007 14:24:56 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 90F2151617; Fri, 2 Feb 2007 17:24:44 -0500 (EST) Date: Fri, 2 Feb 2007 17:24:44 -0500 From: Kris Kennaway To: Pav Lucistnik Message-ID: <20070202222444.GA15313@xor.obsecurity.org> References: <20070202092701.A97555@xorpc.icir.org> <1170441928.33849.9.camel@ikaros.oook.cz> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9jxsPFA5p3P2qPhR" Content-Disposition: inline In-Reply-To: <1170441928.33849.9.camel@ikaros.oook.cz> User-Agent: Mutt/1.4.2.2i Cc: ports@FreeBSD.org, Luigi Rizzo Subject: Re: proper way to handle ports dependencies ? 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: Fri, 02 Feb 2007 22:24:57 -0000 --9jxsPFA5p3P2qPhR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Feb 02, 2007 at 07:45:28PM +0100, Pav Lucistnik wrote: > Luigi Rizzo p??e v p? 02. 02. 2007 v 09:27 -0800: > > I have some ports (linux-gspca-kmod, linux-ov511-kmod, more in the > > future) which depend on linux-kmod-devel which in turn only works > > on i386 and 6.2 or above. > >=20 > > Is it enough to put ONLY_FOR_ARCHS and .if ${OSVERSION} < ... > > just in the parent (linux-kmod-devel), or should i > > put it in all children too ? >=20 > Technically it's enough to put it in the parent port, but it's a service > to the users to put it everywhere, so the process bails out earlier. Actually I prefer only doing it in the parent. Otherwise as these things become more portable over time (e.g. when amd64 came along and gained i386 linux compat), there may be many ports that are now buildable but are forgotten until someone hunts down each and every one of them and makes lots of fixup commits. Kris --9jxsPFA5p3P2qPhR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFw7osWry0BWjoQKURApzAAJ9HT768swLNNV8WsMJl/g7COF+JKwCg+/L3 EmhZSRupvvSsN7SFo5KKRqo= =Jz7T -----END PGP SIGNATURE----- --9jxsPFA5p3P2qPhR--