From owner-freebsd-questions@FreeBSD.ORG Wed Jan 9 18:55:00 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 5A90DEA6 for ; Wed, 9 Jan 2013 18:55:00 +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 E5D24718 for ; Wed, 9 Jan 2013 18:54:59 +0000 (UTC) Received: from seedling.black-earth.co.uk (seedling.black-earth.co.uk [81.2.117.99]) (authenticated bits=0) by smtp.infracaninophile.co.uk (8.14.6/8.14.5) with ESMTP id r09Isg45091997 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 9 Jan 2013 18:54:54 GMT (envelope-from m.seaman@infracaninophile.co.uk) DKIM-Filter: OpenDKIM Filter v2.7.3 smtp.infracaninophile.co.uk r09Isg45091997 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=infracaninophile.co.uk; s=201001-infracaninophile; t=1357757694; bh=EvXYUOapoqK7j2fDHPRZJ4xSbzyYL6KEvn077qPw+4I=; h=Date:From:To:CC:Subject:References:In-Reply-To; z=Date:=20Wed,=2009=20Jan=202013=2018:54:35=20+0000|From:=20Matthew =20Seaman=20|To:=20Walter=20Hurry =20|CC:=20freebsd-questions@freebsd.org|Sub ject:=20Re:=20pkgng=20-=20Symlinks=20created=20by=20portupgrade?|R eferences:=20|In-Reply-To:=20; b=vM/N9t6FQU32u1Vz+wlQBsctWhdf8QntSQ0gAnv5DYtM14gWCOOJrdOBGRcczvQ9j 8Cdl8f/G/XU6446AMqm7SY5sg/knlUQLRLsYTSttz4U5za+7nV6g0uI21bYnzAJAKU OKblI4CFGCFXK/EUeHfIBQRI13NtVHE/nu6YuFW4= Message-ID: <50EDBCEB.7030403@infracaninophile.co.uk> Date: Wed, 09 Jan 2013 18:54:35 +0000 From: Matthew Seaman User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: Walter Hurry Subject: Re: pkgng - Symlinks created by portupgrade? References: In-Reply-To: X-Enigmail-Version: 1.4.6 OpenPGP: id=60AE908C Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig69578F4ABB8E94C6451EBB0C" X-Virus-Scanned: clamav-milter 0.97.6 at lucid-nonsense.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,SPF_FAIL autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on lucid-nonsense.infracaninophile.co.uk Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jan 2013 18:55:00 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig69578F4ABB8E94C6451EBB0C Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 09/01/2013 18:31, Walter Hurry wrote: > I am using pkgng. >=20 > When I issue 'portupgrade -p', after build and installation, = it=20 > builds a new package, as advertised. This (by default) is put into /usr= / > ports/packages/All. >=20 > At the same time, it installs a set of symlinks; one for each relevant = > port category, plus one in /usr/ports/packages/Latest. >=20 > It is the naming of this last in which I am interested. Sometimes the=20 > symlink seems to bear the name (absent the version) of the package, and= =20 > sometimes the name of the port (plus '.txz', of course). >=20 > Two questions: >=20 > 1) Does anyone know the logic used to derive the name of the symlink? >=20 > 2) Would it be considered a breach of etiquette to email the port=20 > maintainer (bdrewery) and ask, or is this regarded as acceptable? >=20 > 'man portupgrade' doesn't seem to shed any light on this, and I am=20 > unaware of where to seek other documentation. The layout of /usr/ports/packages is actually down to the ports system directly and not in the control of any add on software like portupgrade, portmaster or pkgng. The files under /usr/ports/packages/Latest are named according to the LATEST_LINK variable in each port. It's meant to be unique per-port, but falls somewhat short. Various ports have NO_LATEST_LINK set which suppresses creating that link. Cheers, Matthew --=20 Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey JID: matthew@infracaninophile.co.uk --------------enig69578F4ABB8E94C6451EBB0C 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 undefined - http://www.enigmail.net/ iEYEARECAAYFAlDtvPEACgkQ8Mjk52CukIwZnQCfQmDI/LdCHAQGGUxIGM9ugJi4 qxYAoIRGTTOFKcfek129VUFvqjT/QZ6a =lfLj -----END PGP SIGNATURE----- --------------enig69578F4ABB8E94C6451EBB0C--