From owner-freebsd-ports@FreeBSD.ORG Sat Feb 26 18:28:17 2005 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 E67D416A4CE for ; Sat, 26 Feb 2005 18:28:17 +0000 (GMT) Received: from mail.gmx.net (pop.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id E2BDD43D5F for ; Sat, 26 Feb 2005 18:28:16 +0000 (GMT) (envelope-from andreas.kohn@gmx.net) Received: (qmail invoked by alias); 26 Feb 2005 18:28:15 -0000 Received: from unknown (EHLO localhost.localdomain) (212.204.44.203) by mail.gmx.net (mp023) with SMTP; 26 Feb 2005 19:28:15 +0100 X-Authenticated: #2431876 From: Andreas Kohn To: Xin LI In-Reply-To: <1109432372.643.7.camel@spirit> References: <1109421808.10472.17.camel@spirit> <12586C663C1596B0F90D4599@cc-171.int.t-online.fr> <1109432372.643.7.camel@spirit> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-kg7B/kSOteT9Rw/P/tik" Date: Sat, 26 Feb 2005 19:27:46 +0100 Message-Id: <1109442466.88665.95.camel@klamath.syndrom23.de> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 FreeBSD GNOME Team Port X-Y-GMX-Trusted: 0 cc: freebsd-ports@FreeBSD.org cc: Mathieu Arnold Subject: Re: [IDEA] How to represent package version dependencies? 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: Sat, 26 Feb 2005 18:28:18 -0000 --=-kg7B/kSOteT9Rw/P/tik Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sat, 2005-02-26 at 23:39 +0800, Xin LI wrote: > Ah... I just know that from the porters' handbook and bsd.port.mk :-) > I'd personally prefer file:package[< | =3D | > )version][:target] scheme, > since it looks more straightforward. I also like this scheme better. Actually, I was thinking about something similar: I wanted to create some shell script which runs over the ports tree, figures out the current version of a port, and creates a second ports hierarchy from it: /usr/vports/// A Makefile in /usr/vports// would build the latest version, but every versioned port would know against which other port versions it depended, and would use these versions.=20 Some changes to bsd.port.mk (i.e. /usr/ports/Mk/*.mk + patches -> /usr/vports/Mk/*.mk) would have to handle parts of the versioning. Unfortunately, there were many problems that surfaced when thinking about this a little bit more, most of them related to optional dependencies, and management problems, so I did not start actually trying to build this. But at least requiring a certain minimum version would certainly be nice! Regards,=20 Andreas --=-kg7B/kSOteT9Rw/P/tik Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD4DBQBCIL+iYucd7Ow1ygwRAortAKCfUT9o2YhYz6IeM8XSzKpXKZ6RZQCXeZVr FhM7cd5MqHzaBXmgMWE+iA== =GoR6 -----END PGP SIGNATURE----- --=-kg7B/kSOteT9Rw/P/tik--