mail/policyd name conflict
rafan at infor.org
Tue Apr 12 14:33:26 PDT 2005
On Tue, Mar 22, 2005 at 02:33:25PM +0100, Anton Berezin wrote:
> On Tue, Mar 22, 2005 at 09:54:41AM -0300, Marcus Grando wrote:
> > Edwin Groothuis wrote:
> > >I would call them
> > > mail/postfix-policyd
> > > mail/postfix-policyd-spf
> > mail/postfix-policyd-spf
> > mail/postfix-policyd-greylist
> > I like this.
> > After ports freeze, i send PR to change this.
> > But don't forget to change executable name. I change to policyd-spf and
> > the new port change to policyd-greylist or something.
While I'm preparing a new shar for version 1.49, it comes to my
mind that the name conflict things.
As 1.49, it does more things (a helo auto blacking is added), I would
like to have
mail/postfix-policyd-spf (the original mail/policyd)
since greylisting is only part of it. As mentioned before, mail/sqlgrey
and mail/postgrey, will them changed to
A bit long name? If in this case, I would suggest that we don't
touch them and just rename mail/policyd to mail/policyd-spf
and the new one will be mail/policyd (just google policyd, it is
in the second result).
If there is no further problem, I would like to send this rename
pr and policyd 1.49 shar :-)
More information about the freebsd-ports