public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Cc: Jari Aalto <jari.aalto@cante.net>
Subject: Re: msmtp 1.8.5 built using ${prefix}/${SYSCONFDIR}
Date: Wed, 09 Oct 2019 20:10:00 -0000	[thread overview]
Message-ID: <b5a8d728-7da1-97bf-4046-65ad250180f7@cornell.edu> (raw)
In-Reply-To: <20191009200338.GA3790@zebra>

On 10/9/2019 4:03 PM, Stephen Carrier wrote:
> On Wed, Oct 02, 2019 at 01:38:13PM -0600, Brian Inglis wrote:
>> On 2019-10-02 12:18, Stephen Carrier wrote:
>>> On Tue, Oct 01, 2019 at 08:43:40PM -0600, Brian Inglis wrote:
>>>> On 2019-10-01 18:47, Stephen Carrier wrote:
>>>>> The latest verion of the msmtp package: 1.8.5+20190811+git7912c76-1 .
>>>>> Differs from the previous version: 1.6.6-1 .
>>>>>
>>>>> In that the location of the system-wide configuration file is changed
>>>>> from /etc/msmtprc to /usr/etc/msmtprc.
>>>>>
>>>>> I think this has the potential to break installations during an upgrade.
>>>>>
>>>>> In my case it only confused me as I set up a new system.
>>>>>
>>>>> Please consider changing this default back to what it was for the
>>>>> convenience of those who will otherwise need to figure this out.
>>>>
>>>> Definitely not a standard location and nothing there currently on my system.
>>>> The package contents shows only server configuration, nothing on /usr/etc/, no
>>>> defaults provided in /etc/defaults/usr/etc/, and /usr/bin/msmtp-config defaults
>>>> the CONFDIR to /etc, so unless you have a symlink, link or junction from /etc to
>>>> /usr/etc, or changed the location during the server config, /etc/ should have
>>>> been used.
>>>
>>> This is not what I meant.  The package doesn't provide a configuration
>>> file.  msmtp-config generates one in /etc/msmtprc, exactly as I would
>>> want and expect since that's where to find the configuration file for
>>> previous versions.
>>>
>>> The problem is that the binary looks for its configuration file in a
>>> different place:
>>
>>> $ msmtp --version
>>> msmtp version 1.8.5
>>> Platform: x86_64-pc-cygwin
>>> ....
>>> System configuration file name: /usr/etc/msmtprc
>>
>>> and only after I moved the configuration file to that nonstandard location
>>> would msmtp start working instead of complaining that it couldn't find
>>> any configuration file.
>>>
>>> This seems like something that could be fixed by tweaking the package
>>> build scripts; I think it would be great to do that.
>>
>> So this is a discrepancy between the built exe and the config script, which
>> should be resolved by having the built exe use the standard SYSCONFDIR, by
>> removing ${prefix} from its definition.
>> [changing subject]
> 
> Could the package maintainer join in?  I don't see how discussing the
> minutae of the build process actually helps without the maintainer's
> participation.
> 
> Pre-existing msmtp installations use /etc/msmtprc, and the current
> configuration script creates a valid configuration in that same location.
> Clearly, fixing the binary and not the configuration script is the way
> forward, unless there is compelling reason to move the configuration
> file from where it used to be.

I've added the maintainer, Jari Aalto, to the Cc.  I don't think he reads the 
list regularly.

Ken

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2019-10-09 20:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-02  0:47 location of msmtp system-wide configuration Stephen Carrier
2019-10-02  2:43 ` Brian Inglis
2019-10-02 18:18   ` Stephen Carrier
2019-10-02 19:38     ` msmtp 1.8.5 built using ${prefix}/${SYSCONFDIR} Brian Inglis
2019-10-09 20:03       ` Stephen Carrier
2019-10-09 20:10         ` Ken Brown [this message]
2019-10-10 10:09           ` Jari Aalto
2019-10-11  1:45             ` Stephen Carrier

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=b5a8d728-7da1-97bf-4046-65ad250180f7@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=cygwin@cygwin.com \
    --cc=jari.aalto@cante.net \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).