From: Pip Cet <pipcet@protonmail.com>
To: Robert Pluim <rpluim@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: : master 7f97cf31dc3: Create blessmail at build time instead of install time
Date: Fri, 23 Aug 2024 13:03:00 +0000 [thread overview]
Message-ID: <87ttfb75oh.fsf@protonmail.com> (raw)
In-Reply-To: <87bk1js9gm.fsf@gmail.com>
"Robert Pluim" <rpluim@gmail.com> writes:
>>>>>> On Fri, 23 Aug 2024 12:17:26 +0000, Pip Cet <pipcet@protonmail.com> said:
>
> Pip> "Robert Pluim" <rpluim@gmail.com> writes:
> >> branch: master
> >> commit 7f97cf31dc3eb483f84598f61e9f45805f901067
> >> Author: Robert Pluim <rpluim@gmail.com>
> >> Commit: Robert Pluim <rpluim@gmail.com>
> >>
> >> Create blessmail at build time instead of install time
> >>
> >> blessmail is built via the install target, which means it ends up owned
> >> by the user doing the install. It's not installed, so build it at build
> >> time instead.
> >>
> >> Reported by Michael Heerdegen <michael_heerdegen@web.de> in
> >> <https://lists.gnu.org/archive/html/help-gnu-emacs/2024-08/msg00270.html>
> >>
> >> * Makefile.in (install): Move blessmail target from install to actual-all.
>
> Pip> All the patch appears to do is to remove blessmail from 'install', so
> Pip> it's no longer run at all. Maybe there's a second part to it that
> Pip> wasn't committed? Or am I missing something?
>
> Oops. I just pushed the 2nd half of the patch.
I still don't understand this change, I'm afraid. IIUC, the idea is
that this message is printed at install time, not at build time:
Assuming /usr/spool/mail is really the mail spool directory, you should
run lib-src/blessmail /usr/local/libexec/emacs/31.0.50/x86_64-pc-linux-gnu/movemail
as root, to give movemail appropriate permissions.
Do that after running make install.
It's not clear to me that building lib-src/blessmail at build time is
always safe: the user building Emacs might well be in a chroot jail or
restricted so they're unable to access 'rmail-spool-directory'.
As this is really a post-install dependency, I think we need to find a
better way of dealing with it. Maybe we can do without "blessmail"
entirely, and have "blessmail.el" print the full instructions when run,
rather than putting them into "blessmail"?
Pip
next prev parent reply other threads:[~2024-08-23 13:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <172441424046.32730.1198862680597856819@vcs2.savannah.gnu.org>
[not found] ` <20240823115720.C4A92C1FB72@vcs2.savannah.gnu.org>
2024-08-23 12:17 ` master 7f97cf31dc3: Create blessmail at build time instead of install time Pip Cet
2024-08-23 12:35 ` : " Robert Pluim
2024-08-23 13:03 ` Pip Cet [this message]
2024-08-23 16:07 ` : " Robert Pluim
2024-08-24 13:21 ` Pip Cet
2024-08-25 2:50 ` Michael Heerdegen via Emacs development discussions.
2024-08-25 5:10 ` Pip Cet
2024-08-25 5:54 ` Michael Heerdegen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ttfb75oh.fsf@protonmail.com \
--to=pipcet@protonmail.com \
--cc=emacs-devel@gnu.org \
--cc=rpluim@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).