From owner-freebsd-ports@FreeBSD.ORG  Tue Apr 19 03:04:20 2005
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 EE10516A4CE
	for <freebsd-ports@FreeBSD.org>; Tue, 19 Apr 2005 03:04:19 +0000 (GMT)
Received: from infor.ck.tp.edu.tw (infor.ck.tp.edu.tw [203.64.26.200])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 81F8843D54
	for <freebsd-ports@FreeBSD.org>; Tue, 19 Apr 2005 03:04:19 +0000 (GMT)
	(envelope-from llwang@infor.ck.tp.edu.tw)
Received: by infor.ck.tp.edu.tw (Postfix, from userid 1001)
	id D55912DA789; Tue, 19 Apr 2005 11:04:18 +0800 (CST)
Date: Tue, 19 Apr 2005 11:04:18 +0800
From: "Li-Lun Wang (Leland Wang)" <llwang@infor.org>
To: freebsd-ports@FreeBSD.org
Message-ID: <20050419030418.GA25934@Athena.infor.org>
Mail-Followup-To: "Li-Lun Wang (Leland Wang)" <llwang@infor.org>,
	freebsd-ports@FreeBSD.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed
Content-Disposition: inline
User-Agent: Mutt/1.5.6i
Subject: PORTVERSION for a port that depends on the another software
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, 19 Apr 2005 03:04:20 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I have a port (www/ump) that depends on another port (audio/timidity++).
Whenever there is a new version of timidity++ ump needs to be rebuilt.
I had been using PORTREVISION to do this---whenever there is a new
version of timidity++, I bump the PORTREVISION of ump, which I found
quite stupid.

I am thinking if it is a good idea to concatenate the version numbers
of both ports to form the PORTVERSION. For example, the current version
of ump is 1.10, and the current version of timidity++ is 2.13.2, can I
make the PORTVERSION of ump 1.10.2.13.2? What do you think?

- -- Leland Wang
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (FreeBSD)

iD8DBQFCZHUwCQM7t5B2mhARAiqpAJ9bxe1gp4PcWAQZ/ce0PU8mI0jUvgCfbk0H
18Z0io3z1/g4atVNCt6FJ6Q=
=uOcZ
-----END PGP SIGNATURE-----