public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexander Skwar <listen@alexander.skwar.name>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] PORTAGE_ELOG error
Date: Sun, 23 Jul 2006 00:01:34 +0200	[thread overview]
Message-ID: <44C2A03E.4090001@mid.email-server.info> (raw)
In-Reply-To: <20060722214255.065606d3@krikkit.digimed.co.uk>

Neil Bothwick schrieb:
> On Sat, 22 Jul 2006 20:17:46 +0200, Alexander Skwar wrote:
> 
>> I don't know, but it would be a very useful addition - and IMO,
>> they could dump that useless feature, that portage can do SMTP
>> by itself. That's so un-Unix, so Windows-like :(
> 
> Portage doesn't do SMTP by itself, it uses the Python smtplib module.

True.

> Re-using existing software is very unix like

Sending mail with directly speaking SMTP isn't. That's the job
of a MTA.

>> Yes, it would, but I'd actually not suggest to do so. Installing
>> postfix (or any SMTP server, for that matter) just for Portage
>> isn't the right way to go. It's too much code, opening too many
>> potential problems, which can be sidestepped by making
>> portage use /usr/sbin/sendmail instead.
> 
> Why not let portage work with the same SMTP server you use for all other
> mail?

Why make me configure SMTP in two places (MTA and Portage)?

> If your mail client can send mail, why not tell portage to use the
> same route.

Why not make Portage send mail the same way, the MUA
does it - with /usr/sbin/sendmail? That's a standard way
of getting mail off a host.

> There's absolutely no need to use a local MTA if you don't
> already have one.

There's no need to configure the same thing in multiple places.
It's really bad style to make users keep the same configuration
in multiple places.

Alexander Skwar
-- 
This isn't true in practice -- what we've missed out is Stradivarius's
constant.  And then the aside: "For those of you who don't know, that's
been called by others the fiddle factor..."
		-- From a 1B Electrical Engineering lecture.
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-07-22 22:08 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-22 16:21 [gentoo-user] PORTAGE_ELOG error Grant
2006-07-22 16:40 ` Alexander Skwar
2006-07-22 17:07   ` Grant
2006-07-22 18:17     ` Alexander Skwar
2006-07-22 20:42       ` Neil Bothwick
2006-07-22 22:01         ` Alexander Skwar [this message]
     [not found]           ` <20060723120542.228d2b9e@hactar.digimed.co.uk>
2006-07-23 12:27             ` Alexander Skwar
2006-07-23 15:33               ` Neil Bothwick
2006-07-23 19:02                 ` Alexander Skwar
2006-07-24 14:05                   ` Neil Bothwick
2006-07-24 15:06                     ` Alexander Skwar
2006-07-24  5:51 ` Alexander Skwar
2006-07-24 14:44   ` Grant
2006-07-24 15:07     ` Alexander Skwar
2006-07-25 16:52       ` Grant
2006-07-25 17:50         ` Neil Bothwick
2006-07-25 18:16         ` Alexander Skwar
2006-07-25 18:36           ` Grant
2006-07-25 18:42             ` Alexander Skwar
2006-07-25 20:20               ` Mick
2006-07-25 20:38                 ` Alexander Skwar
2006-07-28 17:53             ` Enrico Weigelt
2006-07-24 17:15   ` Tro
2006-07-24 18:08     ` Alexander Skwar
2006-07-24 19:25       ` Mick
2006-07-24 19:57         ` Peter Ruskin
2006-07-24 22:38       ` Alexander Skwar

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=44C2A03E.4090001@mid.email-server.info \
    --to=listen@alexander.skwar.name \
    --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