Re: Installation fails because of mutt_dotlock
On 2005-02-02 18:47:50 +0100, Adeodato Simó wrote:
> There are several ways you can solve this, without patching. The
> easiest would probably be 'fakeroot make install', but I'll assume
> that you don't have it installed.
It installs a mutt_dotlock that doesn't work.
> The thing is that the configure process will try to guess whether you
> need a setgid mutt_dotlock or not, by checking the permissions of the
> default directory for mailboxes. So, if you're building in a system
> where /var/mail is not world writable, configure will conclude that
> you need a setgid mutt_dotlock.
>
> I recommend that you run configure like this:
>
> $ ./configure --with-homespool=mbox --prefix=$HOME/whatever
>
> This will tell mutt that the default mbox is under the user's home
> (~/mbox, in this case) and not /var/mail/$USER,
But this is not true.
> so it will not try to change mutt_dotlock's permissions.
It doesn't even install a mutt_dotlock binary.
> Then, you can always change which
> file is opened by default with the MAIL environment variable (e.g.,
> MAIL=/var/mail/you).
>
> Note, however, that as your /var/mail is not world writable, mutt
> will open such mailbox read only, unless you point your $dotlock_program
> to a suitable one (one with the appropriate permissions, that is).
The documentation says:
6.3.41. dotlock_program
Type: path
Default: "/home/vlefevre/i686-linux/bin/mutt_dotlock"
This file is a symlink to /usr/bin/mutt_dotlock, which is setgid mail.
However, mutt opens /var/mail/lefevre read only.
--
Vincent Lefèvre <vincent@xxxxxxxxxx> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / SPACES project at LORIA