On 11. nov. 2014 14:03, Nigel Kukard wrote:
On 11/11/2014 12:04 PM, Zhang Huangbin wrote:
On Friday, November 7, 2014 at 4:37 PM, Nigel Kukard wrote:
I was working on the Debian packaging a few weeks ago, hopefully soon I
can get the name of the package properly standardized between both v2.0
and v2.1. Right now its a bit of a mess with cbpolicyd vs. policyd vs.
postfix-cluebringer ... we're going to be moving to policyd-cluebringer.
Just taking quite a bit longer than I expected.
Just curious, why not use "cluebringer" directly?
Well, it supposed to be "policyd", "cluebringer" was its codename.
Thing is to make it more universal and easy to understand when I replace
postfix-policyd in Debian, my idea was to change its name to
policyd-cluebringer.
I always thought policyd was a pretty lousy name. Way too generic. The
mechanism it provides is a "policy daemon" as specified in the postfix
manual. There are quite a few such, and ad-hoc perl scripts that play
that role tend to get named "policyd" as well. As a package both the
terms "postfix" and "cluebringer" should be part of the name, IMHO. At
least keep the "cluebringer" please.
I touch my postfix setup maybe every 6 months, and the first couple of
years after cluebringer came out I had to redo my research on policy
handling each time, because I could not get my head around the naming of
the various parts of my setup (way too complicated, , but KISS is boring
:) )
_______________________________________________
Users mailing list
[email protected]
http://lists.policyd.org/mailman/listinfo/users_lists.policyd.org
