Re: pkgng vs random port moves

2014-03-16 Thread olli hauer
On 2014-03-16 21:51, J David wrote: > On Sun, Mar 16, 2014 at 3:45 PM, olli hauer wrote: >> run the following command and pkgng will take care of the renamed port. >> #> pkg set -o mail/p5-Mail-SpamAssassin:mail/spamassassin > > That works perfectly. Thanks very much! I've just added the missi

Re: pkgng vs random port moves

2014-03-16 Thread J David
On Sun, Mar 16, 2014 at 3:45 PM, olli hauer wrote: > run the following command and pkgng will take care of the renamed port. > #> pkg set -o mail/p5-Mail-SpamAssassin:mail/spamassassin That works perfectly. Thanks very much! ___ freebsd-ports@freebsd.o

Re: pkgng vs random port moves

2014-03-16 Thread olli hauer
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,

pkgng vs random port moves

2014-03-16 Thread J David
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