Justin Pryzby <[EMAIL PROTECTED]> writes:
> This is at least true for the "debconf" errors; since "debconf is a
> cache", it isn't useful to fail when the cache has already been removed.
> I guess this is why some packages use:
> . /usr/share/debconf/confmodule || true
> They should really use
> f=/usr/share/debconf/confmodule
> [ ! -e $f ] || . $f;
I assume the reason why the second is better is to avoid the error
message? (BTW, I hope maintainers don't use the second as written rather
than the much clearer:
if [ -e /usr/share/debconf/confmodule ] ; then
. /usr/share/debconf/confmodule
fi
There's no need to be obfuscated.)
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
