From: Danny Milosavljevic <dannym@scratchpost.org>
To: 35008@debbugs.gnu.org
Cc: Brant Gardner <brantcgardner@brantware.com>
Subject: bug#35008: sendmail package installs in wrong path
Date: Tue, 26 Mar 2019 20:50:22 +0100 [thread overview]
Message-ID: <20190326205022.68d0ccd4@scratchpost.org> (raw)
In-Reply-To: <20190326191827.wshwrxvh4bxonvit@tethys.gardner.local>
[-- Attachment #1: Type: text/plain, Size: 1241 bytes --]
Hi,
On Tue, 26 Mar 2019 14:18:27 -0500
Brant Gardner <brantcgardner@brantware.com> wrote:
> Good afternoon;
>
> Installing sendmail package as:
>
> (packages (cons* nss-certs ;for HTTPS access
> ; (several other packages here)
> sendmail
> %base-packages))
>
> Results in sendmail installing in this location:
>
> /gnu/store/b0gmd1ac6np7zgb8hvbfgy45b0haz8xg-sendmail-8.15.2/usr/sbin/sendmail
>
> But no links for sendmail show up under any user's profile, and asking on #guix seems to
> indicate that sendmail should install under /usr/bin, not /usr/sbin which may be the issue.
What's more important is that it shouldn't have "/usr" (in a way,
"/gnu/store/b0gmd1ac6np7zgb8hvbfgy45b0haz8xg-sendmail-8.15.2" is "/usr" already).
./devtools/M4/UNIX/defines.m4 seems to contain a lot of path definitions but we
don't patch them. That is definitely incorrect.
confMBINDIR seems to be the variable used for installation (see sendmail/Makefile.m4).
(I have no idea what ${M`'BINDIR}, used in there, does)
As I don't know sendmail (always been a postfix / qmail user), I can't help more than that,
but maybe someone else can adapt and test it.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-03-26 20:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 19:18 bug#35008: sendmail package installs in wrong path Brant Gardner
2019-03-26 19:50 ` Danny Milosavljevic [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190326205022.68d0ccd4@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=35008@debbugs.gnu.org \
--cc=brantcgardner@brantware.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.