From owner-freebsd-ports@FreeBSD.ORG Tue Jun 1 11:01:38 2004 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 D95DE16A4CE for ; Tue, 1 Jun 2004 11:01:38 -0700 (PDT) Received: from hood.oook.cz (hood.oook.cz [212.27.205.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C7DC43D1D for ; Tue, 1 Jun 2004 11:01:38 -0700 (PDT) (envelope-from pav@FreeBSD.org) Received: from hood.oook.cz (localhost.oook.cz [127.0.0.1]) by hood.oook.cz (8.12.11/8.12.11) with ESMTP id i51I1Dgl020870; Tue, 1 Jun 2004 20:01:13 +0200 (CEST) (envelope-from pav@FreeBSD.org) Received: (from pav@localhost) by hood.oook.cz (8.12.11/8.12.11/Submit) id i51I1Cqs020869; Tue, 1 Jun 2004 20:01:12 +0200 (CEST) (envelope-from pav@FreeBSD.org) X-Authentication-Warning: hood.oook.cz: pav set sender to pav@FreeBSD.org using -f From: Pav Lucistnik To: Tim Bishop In-Reply-To: <20040601150959.GA83834@carrick.bishnet.net> References: <20040601150959.GA83834@carrick.bishnet.net> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-0fc/RgQk04M4DYR2iMhm" Message-Id: <1086112872.41198.5.camel@hood.oook.cz> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Tue, 01 Jun 2004 20:01:12 +0200 cc: freebsd-ports@FreeBSD.org Subject: Re: Port has different versions for different architectures... X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: pav@FreeBSD.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jun 2004 18:01:39 -0000 --=-0fc/RgQk04M4DYR2iMhm Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: quoted-printable V =FAt, 01. 06. 2004 v 17:09, Tim Bishop p=ED=B9e: > Say a new version of a package has been released for one arcitecture, > but not others, how can this be dealt with in a port? >=20 > I'd want to do something _like_ this (but not this): >=20 > .if ${ARCH} =3D=3D "i386" > PORTVERSION=3D1.1 > .else > PORTVERSION=3D1.0 > .endif >=20 > I'm sure there are numerous bodges to doing this in the port, but I > suspect this will break things such as the INDEX file. No, it will not break INDEX file. It will just result in different INDEX file for each architecture. > A solution would be to maintain multiple versions of the same port, but > that seems like overkill. Unless slave ports are used? If plist don't change between versions, I don't see much problems with your approach. Otherwise you can wait with the update until all archs are available, or temporarily comment out laging architectures. --=20 Pav Lucistnik I went grocery shopping, made a pot of chilli, played ey, then ate some chilli --=-0fc/RgQk04M4DYR2iMhm Content-Type: application/pgp-signature; name=signature.asc Content-Description: Toto je =?iso-8859-2?Q?digit=E1ln=EC?= =?ISO-8859-1?Q?_podepsan=E1?= =?iso-8859-2?Q?_=E8=E1st?= =?ISO-8859-1?Q?_zpr=E1vy?= -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBAvMRontdYP8FOsoIRAsK1AJ4/2uDIw7Ln9oGjYz6XoY9DPFbR0ACfY3uJ Sxz17Z6erCZQXDRwrhyoEKU= =7IMs -----END PGP SIGNATURE----- --=-0fc/RgQk04M4DYR2iMhm--