svn commit: r347936 - in head: . japanese japanese/p5-Mail-SpamAssassin japanese/spamassassin mail mail/claws-mail-spamassassin mail/evolution mail/exim mail/isbg mail/mailscanner mail/mimedefang m...

[Andrej Zverev]

On Wed, Mar 12, 2014 at 4:46 PM, Bryan Drewery <bdrewery at freebsd.org> wrote:
> On 3/11/2014 9:56 PM, Andrej Zverev wrote:
>> I think since p5-Mail-SA has a long history in ports tree, you
>> (can/need/good idea) also send short annonce of such changes to
>> port-announce@ and ports@ maillists.
>
> No, MOVED is sufficient. We never send ports@ or ports-announce@ for
> renamed origins. Even UPDATING is not conventional in this case.

Sure, I'm just worry about people who can read some sort or article
about spamassassin and FreeBSD ( cd /usr/ports/mail/no-more-here &&
try another disto )
But I'm not ready to say more in support of this observation :-)

>
> I do agree with this change and wish we did similar on all other leaf
> application ports. p5-* py-* rubygem-* to me mean very specifically that
> they are libraries/dependencies/plugins/modules. Leaf applications
> having a lang- qualifier on them is very confusing as upstreams do not
> use it and they look like they are libraries, ie, p5-Mail-SpamAssassin
> looks like something you could include in a perl script to use
> spamassassin, not spamassassin itself.

Well, you can use SA libraries actually. At least now i can quick find
something from CPAN since i know how origin formed.
With your solution I need mapping. Sure pkg have answers for all my
questions, but people still using ports, grepping pkg-plist's not so
fun.

>
> If this port includes both it should be split up into a library and the
> leaf application.

Are you planing to make own release team for 3rd party software? Or
you know legal way to clone us to fill human resources?