On 09/01/2013 18:31, Walter Hurry wrote: > I am using pkgng. > > When I issue 'portupgrade <package> -p', after build and installation, it > builds a new package, as advertised. This (by default) is put into /usr/ > ports/packages/All. > > At the same time, it installs a set of symlinks; one for each relevant > port category, plus one in /usr/ports/packages/Latest. > > It is the naming of this last in which I am interested. Sometimes the > symlink seems to bear the name (absent the version) of the package, and > sometimes the name of the port (plus '.txz', of course). > > Two questions: > > 1) Does anyone know the logic used to derive the name of the symlink? > > 2) Would it be considered a breach of etiquette to email the port > maintainer (bdrewery) and ask, or is this regarded as acceptable? > > 'man portupgrade' doesn't seem to shed any light on this, and I am > 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 -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey JID: matt...@infracaninophile.co.uk
signature.asc
Description: OpenPGP digital signature