From owner-freebsd-x11@FreeBSD.ORG Tue May 9 16:34:31 2006 Return-Path: X-Original-To: freebsd-x11@FreeBSD.org Delivered-To: freebsd-x11@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EE1B816A759 for ; Tue, 9 May 2006 16:34:31 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id ADB9D43D55 for ; Tue, 9 May 2006 16:34:18 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 919381A3C25; Tue, 9 May 2006 09:34:18 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 054CF5157B; Tue, 9 May 2006 12:34:18 -0400 (EDT) Date: Tue, 9 May 2006 12:34:17 -0400 From: Kris Kennaway To: Dejan Lesjak Message-ID: <20060509163417.GE89331@xor.obsecurity.org> References: <200605071756.k47HuSvD033837@8ball.rtp.FreeBSD.org> <200605091804.33074.dejan.lesjak@ijs.si> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="n+lFg1Zro7sl44OB" Content-Disposition: inline In-Reply-To: <200605091804.33074.dejan.lesjak@ijs.si> User-Agent: Mutt/1.4.2.1i Cc: freebsd-x11@FreeBSD.org, Kris Kennaway Subject: Re: Ports with duplicate LATEST_LINKS X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 May 2006 16:34:44 -0000 --n+lFg1Zro7sl44OB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, May 09, 2006 at 06:04:32PM +0200, Dejan Lesjak wrote: > On Sunday 07 May 2006 19:56, Kris Kennaway wrote: > > Dear port maintainers, > > > > The following list includes ports maintained by you that have duplicate > > LATEST_LINK values. They should either be modified to use a unique > > LATEST_LINK or suppressed using NO_LATEST_LINK, to avoid overwriting > > each other in the packages/Latest directory. If your ports conflict wi= th > > ports maintained by another person, please coordinate your efforts with > > them. > > > > > > Thanks, > > Kris "Annoying Reminder Guy II" Kennaway > > LATEST_LINK PORTNAME MAINTAINER > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D > > git devel/git anholt@FreeBSD.org > > git misc/git ports@FreeBSD.org > > imake devel/imake-4 x11@FreeBSD.org > > imake devel/imake-6 x11@FreeBSD.org >=20 > IIRC it was agreed that since imake-4 and imake-6 don't both produce pack= ages=20 > on same FreeBSD version LATEST_LINK could stay as it is for both. Is it s= till=20 > OK if things stay like this or should ports/96293 be committed? (Or was i= t=20 > never OK and I just misremembered?) I'd prefer the warning to be silenced. You can either commit the PR or make the LATEST_LINK conditional on X_WINDOW_SYSTEM being set (i.e. for xorg have the LATEST_LINK in imake-4 and vice versa). That will be a NOP, but it will shut up the script. Kris --n+lFg1Zro7sl44OB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEYMSJWry0BWjoQKURAoI1AJ9b7VNwD8X1cB0oSmWdE0Zx3RDAVgCfbudG kN8brm1VIrpLpwnvoGXGIG0= =BJgW -----END PGP SIGNATURE----- --n+lFg1Zro7sl44OB--