Date: Fri, 2 Feb 2007 17:24:44 -0500 From: Kris Kennaway <kris@obsecurity.org> To: Pav Lucistnik <pav@FreeBSD.org> Cc: ports@FreeBSD.org, Luigi Rizzo <rizzo@icir.org> Subject: Re: proper way to handle ports dependencies ? Message-ID: <20070202222444.GA15313@xor.obsecurity.org> In-Reply-To: <1170441928.33849.9.camel@ikaros.oook.cz> References: <20070202092701.A97555@xorpc.icir.org> <1170441928.33849.9.camel@ikaros.oook.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
--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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070202222444.GA15313>