From owner-freebsd-ports@FreeBSD.ORG Mon Jun 11 11:34:33 2012 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AB636106564A; Mon, 11 Jun 2012 11:34:33 +0000 (UTC) (envelope-from m.seaman@infracaninophile.co.uk) Received: from smtp.infracaninophile.co.uk (smtp6.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3cd3:cd67:fafa:3d78]) by mx1.freebsd.org (Postfix) with ESMTP id C1F978FC26; Mon, 11 Jun 2012 11:34:32 +0000 (UTC) Received: from seedling.black-earth.co.uk (seedling.black-earth.co.uk [81.187.76.163]) (authenticated bits=0) by smtp.infracaninophile.co.uk (8.14.5/8.14.5) with ESMTP id q5BBYSJo078483 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 11 Jun 2012 12:34:29 +0100 (BST) (envelope-from m.seaman@infracaninophile.co.uk) X-DKIM: OpenDKIM Filter v2.5.2 smtp.infracaninophile.co.uk q5BBYSJo078483 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=infracaninophile.co.uk; s=201001-infracaninophile; t=1339414469; bh=X/VyJJoEGmoGowHm7jS/KAWvAE9H1NjyQJ8fMAqV78Y=; h=Date:From:To:CC:Subject:References:In-Reply-To:Content-Type: Message-ID:Mime-Version; b=zNaoiDnFSyWOH4cgBuwrbQdzl83Y2/vtxrFvjvTLmdmOnXReZIRfaZCCLpD7SdoSH 8rShdhtB50Ey1i/HPFvzE2aP8+ubbr2tJocCg/li7m/0WOzOQk9tc+mSLp03pGCdRM LhTwnofu50XqeoUIQYI4DTdsrs/UMnjb7u2cb6uQ= Message-ID: <4FD5D7B8.9080504@infracaninophile.co.uk> Date: Mon, 11 Jun 2012 12:34:16 +0100 From: Matthew Seaman User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:13.0) Gecko/20120601 Thunderbird/13.0 MIME-Version: 1.0 To: Baptiste Daroussin References: <20120611043001.GO60433@ithaqua.etoilebsd.net> <4FD591DF.3060808@infracaninophile.co.uk> <20120611103221.GU60433@ithaqua.etoilebsd.net> In-Reply-To: <20120611103221.GU60433@ithaqua.etoilebsd.net> X-Enigmail-Version: 1.4.2 OpenPGP: id=60AE908C Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig7DAD64CC3C9D3B7795A1D430" X-Virus-Scanned: clamav-milter 0.97.4 at lucid-nonsense.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-1.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, DKIM_ADSP_ALL,DKIM_SIGNED,T_DKIM_INVALID autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on lucid-nonsense.infracaninophile.co.uk Cc: ports@freebsd.org Subject: Re: ports need a uniq identifier, do you have any suggestion? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2012 11:34:33 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig7DAD64CC3C9D3B7795A1D430 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 11/06/2012 11:32, Baptiste Daroussin wrote: >> UNIQUENAME importance being because the default location for a port's >> > OPTIONSFILE is derived from it, and non-uniqueness can lead to ports= >> > fighting over control of that file? Which is bad when unintentional= , >> > but can be useful for some related ports to share the same options s= ettings. > Well this is the right thing to do but looking at bsd.port.mk and the c= hanges > needed I get bored and gave up :( I haven't looked at what would be necessary to fix UNIQUENAME collisions in any great detail, but I think a number are due to setting PORTNAME to something basically incorrect. >> > Does pkgng really need LATEST_LINK at all? As far as I recall, that= >> > only exists so that the user can say: > Well no pkgng doesn't need it at all except for pkg itself for the boot= strap :) Hmmm... so there just has to be pkg.txz at some predictable URL(s) on the FBSD mirrors? That doesn't sound like enough to justify keeping LATEST_LINK related bits in the ports tree. >> > I don't see the problem with port prefixes changing UNIQUENAME. Isn= 't >> > py27-foo conceptually a different port to py30-foo ? Yes, they are >> > built from the same port ORIGIN, but you already intend dropping the= >> > one-to-one correspondence between port ORIGINS and packages with the= >> > introduction of sub-ports. > Maybe they are different packages, but they have the same options, and = from > pkgng we should be able to detect it as the same package just a differe= nt > runtime which is what they are. I think I see. You're thinking of packages that install the same files, but maybe in a different location (eg. SITE_PERL) or that register run-time dependencies on a number of different possible providers. Couldn't that boil down to having several alternate .MANIFEST files in the pkg? Plus some sort of final-location-independent way of naming the files to be installed by the package? On the matter of having alternate RUN_DEPENDS to be set at install time? I've wanted to do something like that with databases/phpmyadmin for ages. Most of the optional dependencies there are autodetected by the PHP code at run-time, so it should be possible to just ask the user which of them they want to have during pkg installation. Cheers, Matthew --=20 Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matthew@infracaninophile.co.uk Kent, CT11 9PW --------------enig7DAD64CC3C9D3B7795A1D430 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.16 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/V18QACgkQ8Mjk52CukIxHBACfZ39I2HAY+dmx56DvTUojCuLy OkAAoIJ3GJWj2y8CcyoufwgOYeU0oBWx =f1wY -----END PGP SIGNATURE----- --------------enig7DAD64CC3C9D3B7795A1D430--