Summary: | acct-user/mail: /var/spool/mail should be /var/mail | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jonas Stein <jstein> |
Component: | Current packages | Assignee: | Gentoo Quality Assurance Team <qa> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | conikost, eras, floppym, jstein |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Jonas Stein
2022-04-10 19:35:25 UTC
> It is important to note that there is no requirement to physically move the mail spool to this location. However, programs and header files must be changed to use /var/mail."
Sounds like we should just symlink /var/mail to /var/spool/mail.
(In reply to Mike Gilbert from comment #1) > Sounds like we should just symlink /var/mail to /var/spool/mail. and we do via net-mail/mailbase (In reply to Jonas Stein from comment #0) > However, programs and header files must be > changed to use /var/mail." Noted. OK. (In reply to Mike Gilbert from comment #1) > Sounds like we should just symlink /var/mail to /var/spool/mail. Or the other way around? What is the advantage of having it in /var/spool/mail, other than backwards compatibility? (In reply to Ulrich Müller from comment #3) It's easier/safer to create a symlink than to move data. (In reply to Mike Gilbert from comment #4) > It's easier/safer to create a symlink than to move data. Right. That's the backwards compatibility argument (and probably it doesn't matter much which way around the symlink is). (In reply to Jonas Stein from comment #0) > This change is important for inter-operability since a single /var/mail is > often shared between multiple hosts and multiple UNIX distribution (despite > NFS locking issues). I wonder how many people do that in 2022. :) The symlink direction matters for existing systems that already have data stored in /var/spool/mail. The data would need to moved somehow before the symlink is created at /var/spool/mail. (In reply to Mike Gilbert from comment #6) > The symlink direction matters for existing systems that already have data > stored in /var/spool/mail. The data would need to moved somehow before the > symlink is created at /var/spool/mail. I don't think that we actually disagree here. For the functionality, it doesn't matter if we have /var/mail -> spool/mail or /var/spool/mail -> ../mail, and backwards compatibility prefers the former. The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c47ea1f2cf76cd9ef093eea23c795a109dd4e4ca commit c47ea1f2cf76cd9ef093eea23c795a109dd4e4ca Author: Eray Aslan <eras@gentoo.org> AuthorDate: 2022-04-22 08:29:56 +0000 Commit: Eray Aslan <eras@gentoo.org> CommitDate: 2022-04-22 08:36:00 +0000 mail-mta/postfix: add 3.8_pre20220421, drop 3.8_pre20220417 configure mail_spool_directory as /var/mail instead of /var/spool/mail Bug: https://bugs.gentoo.org/837707 Signed-off-by: Eray Aslan <eras@gentoo.org> mail-mta/postfix/Manifest | 2 +- ...stfix-3.8_pre20220417.ebuild => postfix-3.8_pre20220421.ebuild} | 7 +++++-- 2 files changed, 6 insertions(+), 3 deletions(-) |