Re: Remove absolute paths from gpg.rc
On Sat, Mar 17, 2007 at 01:16:38AM +0100, Vincent Lefevre wrote:
> On 2007-03-17 08:16:15 +1100, Cameron Simpson wrote:
> > On 15Mar2007 20:25, David Champion <dgc@xxxxxxxxxxxx> wrote:
> > > I can think of two compromises:
> > > * as Thomas Dickey suggested, detect gpg at compile time and insert
> > > the correct path into the installed muttrc files;
> > I would vote for this one. Maybe insert /usr/bin (and other standard
> > places, by OS distribution) at the front of the $PATH _during_ the
> > detection phase to reduce user $PATH weirdness trouble. And supply a
> > configure --with-gpg= to specify a path to override the detector, if
> > there's one in configure.
> The detector could be wrong. For instance, the user may want to install
> a new (more secure) version in /usr/local later (and have /usr/local/bin
> before /usr/bin in his $PATH). If Mutt still uses /usr/bin/gpg, this is
> bad.
Yeah, but we're talking about the installed examples, not a hard-coded
path that mutt will always use.
I think it's reasonable to set a sane-ish default in the example, and
assume that if the user prefers to install in a different place later
on, they can make the appropriate change in their .muttrc.
w