Mailing-List: contact dev-help@spamassassin.apache.org; run by ezmlm
Precedence: bulk
From: bugzilla-daemon@bugzilla.spamassassin.org
To: dev@spamassassin.apache.org
Subject: [Bug 6268] [review] SA die()s if  can't create the userstate dir
In-Reply-To: <bug-6268-26@https.issues.apache.org/SpamAssassin/>
References: <bug-6268-26@https.issues.apache.org/SpamAssassin/>
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
Message-Id: <20100111163803.BEC7B234C1EE@brutus.apache.org>
Date: Mon, 11 Jan 2010 08:38:03 -0800 (PST)

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6268

--- Comment #7 from Kevin A. McGrail <kmcgrail@pccc.com> 2010-01-11 08:38:02 UTC ---
(In reply to comment #6)
> +1
> 
> I don't mind the proposed change die->dbg, although the original change
> was not unintentional. As an admin I'd be worried if some application tries
> to write into /root (but fails), or if what is supposed to be a directory
> turns out to be a regular file or worse (pipe, special device) - and
> would prefer to be boldly notified by the application about such a failure.

+1 - Also, the dbg to die change being an API change that is affecting
real-world applications using the API, the change should be considered
carefully and if necessary documented in an incompatibilities section / Changes
/ Readme.  I'm not opposed to the change but would recommend it delay the
release of 3.3.0 to give API integrators a chance to prepare compatible
releases.

Amavis and MIMEDefang, for example, come to mind.

FYI, DFS of MD has also given lazy consensus to the die to dbg change.

-- 
Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.