From owner-freebsd-ports@FreeBSD.ORG  Tue Jun  1 08:10:14 2004
Return-Path: <owner-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 8FF3E16A4CE
	for <freebsd-ports@freebsd.org>; Tue,  1 Jun 2004 08:10:14 -0700 (PDT)
Received: from carrick.bishnet.net (carrick.bishnet.net [217.204.9.201])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 467B043D49
	for <freebsd-ports@freebsd.org>; Tue,  1 Jun 2004 08:10:14 -0700 (PDT)
	(envelope-from tdb@carrick.bishnet.net)
Received: from tdb by carrick.bishnet.net with local (Exim 4.33; FreeBSD)
	id 1BVAtr-0003EA-I7
	for freebsd-ports@freebsd.org; Tue, 01 Jun 2004 16:09:59 +0100
Date: Tue, 1 Jun 2004 16:09:59 +0100
From: Tim Bishop <tim-lists@bishnet.net>
To: freebsd-ports@freebsd.org
Message-ID: <20040601150959.GA83834@carrick.bishnet.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.2.1i
X-PGP-Key: 0x5AE7D984
X-PGP-Fingerprint: 1453 086E 9376 1A50 ECF6  AE05 7DCE D659 5AE7 D984
Sender: "T.D.Bishop" <tdb@carrick.bishnet.net>
X-Bishnet-MailScanner-Information: Contact postmaster@bishnet.net
X-Bishnet-MailScanner-VirusCheck: Found to be clean
X-Bishnet-MailScanner-From: tdb@carrick.bishnet.net
Subject: Port has different versions for different architectures...
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Jun 2004 15:10:14 -0000

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?

I'd want to do something _like_ this (but not this):

.if ${ARCH} == "i386"
PORTVERSION=1.1
.else
PORTVERSION=1.0
.endif

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.

A solution would be to maintain multiple versions of the same port, but
that seems like overkill. Unless slave ports are used?

Any thoughts?

Tim.

-- 
Tim Bishop
http://www.bishnet.net/tim
PGP Key: 0x5AE7D984