[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Pre-approval for squirrelmail-plugins



Dear release team,

I tried to discuss this with my sponsor (in CC) but he didn't answer for
a few days and to not delay release I want to ask you directly:

I'm maintaing a few squirrelmail plugins which are automatically
activated in postinst (and deactivated in postrm). When I reviewed my
packages a few days ago I noticed that I corrected two of them. They all
used a command-with-path-in-maintainer-script (lintian warning), now two
of them don't while the others still do.

This is normally not a big deal but I could imagine that someone for
whatever reasons changes his squirrelmail-configure and copies it to
/usr/local/bin. Then two plugins would use that one and others wouldn't.
That *could* in *some* situations [1] lead to unexpected behaviour.

So, change squirrelmail-{lockout,logger,quicksave,secure-login,sent-
confirmation,spam-buttons,viewashtml}, or not? All updates could be done
via unstable.

Hauke

[1] I don't know why someone would do that but he/she could.

Attachment: signature.asc
Description: Digital signature


Reply to: