From owner-freebsd-ports@FreeBSD.ORG  Sun Mar 16 19:45:08 2014
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id D9375E16
 for <freebsd-ports@freebsd.org>; Sun, 16 Mar 2014 19:45:08 +0000 (UTC)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 6F09EC28
 for <freebsd-ports@freebsd.org>; Sun, 16 Mar 2014 19:45:07 +0000 (UTC)
Received: from [192.168.0.100] ([87.139.233.65]) by mail.gmx.com (mrgmx001)
 with ESMTPSA (Nemesis) id 0M4GRv-1XG8Ua1ojT-00rlAO; Sun, 16 Mar 2014 20:44:59
 +0100
Message-ID: <5325FF45.2080106@gmx.de>
Date: Sun, 16 Mar 2014 20:45:09 +0100
From: olli hauer <ohauer@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 5.1;
 rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: freebsd-ports@freebsd.org
Subject: Re: pkgng vs random port moves
References: <CABXB=RQw8eFo6VxFQJbbyTcjDmnkocNP+u7xXx2tFZEnyx8=sg@mail.gmail.com>
In-Reply-To: <CABXB=RQw8eFo6VxFQJbbyTcjDmnkocNP+u7xXx2tFZEnyx8=sg@mail.gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:wSghthkofdb/6x7+VDho/4kTwvpc4mLrOlIJ0X08ib4tpdlRTlX
 85tHmGa+ofU+1VmMR/cPCEnsrs8swbzYYquZ1bLW1PblDkQZLfvLzQNNZauJ1RmEqBHf2H7
 c2HfCobRQtLu5UumltiTiKTYlCItnJEZABWf1TxJXjZ+s3y/gkRqs1ogjaXFThPGs2hCjVJ
 kDT2rUdfRztKIvKAZzdPA==
Cc: J David <j.david.lists@gmail.com>
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/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: Sun, 16 Mar 2014 19:45:08 -0000

On 2014-03-16 18:50, J David wrote:
> Is there a best practice for what to do with pkgng when ports
> maintainers randomly rename ports? (E.g. mail/p5-Mail-SpamAssassin
> being moved to mail/spamassassin a few days ago without notice or
> warning or documentation in UPDATING.)
> 
> Prior to pkgng, we used to use pkg_replace for this.  portmaster also
> has an option for it.  But pkgng seems to assume that never happens
> which is (unfortunately) not a valid assumption.
> 
> Thanks for any advice!

Hi David,

run the following command and pkgng will take care of the renamed port.
#> pkg set -o mail/p5-Mail-SpamAssassin:mail/spamassassin

The syntax is similar to the one from portmaster

pkgng: pkg set -o $old:$new
portmaster: portmaster -o $new $old


Unluckily for spamassassin there is only an entry in ports/MOVED an no
instructions in ports/UPDATING.

-- 
Regards,
olli