public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Gilbert <floppym@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Heads up: Gentoo fouls up mail transport agent.
Date: Sat, 21 Jul 2018 18:10:58 -0400	[thread overview]
Message-ID: <CAJ0EP42RKzaqbVZ7FLU1Nouih+btvozi+mBFzNLc6xmTFdik7w@mail.gmail.com> (raw)
In-Reply-To: <20180721210302.GB24559@ACM>

On Sat, Jul 21, 2018 at 5:03 PM, Alan Mackenzie <acm@muc.de> wrote:
> Hello, Gentoo.
>
> Right at the moment, I feel a lot of sympathy with Alan Grimes, and need
> a lot of restraint in avoiding the use of swear words in describing some
> Gentoo developer.
>
> ...
>
> nullmailer installs a file /usr/sbin/sendmail.  This masks out the
> correct /usr/bin/sendmail (which is a symbolic link to s/qmail, which I
> installed by hand, not using emerge) because /usr/sbin is before
> /usr/bin in $PATH.
>
> ...
>
> But what's the proper method to tell my gentoo system that I don't want
> crud like nullmailer installed?  How can I guard myself against such
> presumptiousness on the part of the Gentoo devs in the future?

You must have installed a package that depends on virtual/mta,
presumably because it needs to send emails. Had you installed qmail
using portage, the virtual/mta dep would have been satisfied by it,
and nullmailer would not have been installed in the first place.
However, you didn't do that, and so portage had no idea qmail was
installed.

A possible workaround would be to add mail-mta/netqmail to
package.provided on your system. However, there's still no guarantee
that your custom-built qmail software will work with other packages
provided by Gentoo.

Regarding your accusations: Gentoo developers cannot anticipate every
possible thing you might do on your system, especially when you start
installing custom programs in paths that are traditionally managed by
our package manager. Using portage you can customize your system
extensively, without needing to custom build your own software. If
that's not good enough for you, go build a Linux from Scratch system
and enjoy the lack of any package management or support whatsoever.


  reply	other threads:[~2018-07-21 22:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-21 21:03 [gentoo-user] Heads up: Gentoo fouls up mail transport agent Alan Mackenzie
2018-07-21 22:10 ` Mike Gilbert [this message]
2018-07-22  5:46   ` François-Xavier CARTON
2018-07-22 10:19     ` Alan Mackenzie
2018-07-22 10:57   ` Alan Mackenzie
2018-07-22 12:53     ` Rich Freeman
2018-07-22 22:22       ` Walter Dnes
2018-07-22 12:57     ` Mike Gilbert
2018-07-21 22:20 ` Ralph Seichter
2018-07-22 11:06   ` Alan Mackenzie
2018-07-21 23:04 ` [gentoo-user] " Grant Edwards
2018-07-22  2:11   ` Ian Zimmerman
2018-07-22  7:27     ` Kai Peter
2018-07-22 10:24       ` Ralph Seichter
2018-07-23  6:56         ` Kai Peter
2018-07-23 11:22           ` Ralph Seichter
2018-07-22 13:32 ` Nikos Chantziaras

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=CAJ0EP42RKzaqbVZ7FLU1Nouih+btvozi+mBFzNLc6xmTFdik7w@mail.gmail.com \
    --to=floppym@gentoo.org \
    --cc=gentoo-user@lists.gentoo.org \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox