DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 5244C3858CD1
Message-ID: <5ec6f2b3-bcb9-9a9c-095b-0d4cb45c9089@dronecode.org.uk>
Date: Fri, 23 Jun 2023 13:35:51 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101
 Thunderbird/102.12.0
Subject: Re: git submodule + gettext / envsubst
To: Adam Dinwoodie <adam@dinwoodie.org>,
        The Cygwin Mailing List <cygwin@cygwin.com>
References: <000101d9a5a8$8b78d160$a26a7420$@uni-bremen.de>
 <CA+kUOamhXV2Y1ncOtLbu1+zQ_sSMhKRrZSdgNmZNnoBj8N2YEw@mail.gmail.com>
Content-Language: en-GB
In-Reply-To: <CA+kUOamhXV2Y1ncOtLbu1+zQ_sSMhKRrZSdgNmZNnoBj8N2YEw@mail.gmail.com>
Precedence: list
From: Jon Turney via Cygwin <cygwin@cygwin.com>
Reply-To: Jon Turney <jon.turney@dronecode.org.uk>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Errors-To: cygwin-bounces+archive-cygwin=delorie.com@cygwin.com
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie.com@cygwin.com>
Content-Transfer-Encoding: 8bit

On 23/06/2023 11:11, Adam Dinwoodie via Cygwin wrote:
> On Fri, 23 Jun 2023 at 08:59, Andreas Heckel via Cygwin wrote:
>>
>> Hi,
>>
>> I recently faced some error messages when using git submodules. I found, that Cygwin's git works nicely on its own. But when I have MSYS binary paths in my environment, Cygwin's git finds the msys gettext and envsubst binary and tries to use it, resulting in error messages (see below). I did solve the issue, by installing Cygwin's gettext (which git does not seem to be requiring).
>> I write, because I found it somewhat odd, that Cygwin's git is not dependent on gettext, but uses it, if it finds it somewhere in the path environment. Just to emphasize, in my Cygwin environment all Cygwin paths come first. So it was only using the wrong msys binary, because there was none in Cygwin.
>> Is this behaviour expected and intended or could it be mitigated during installation somehow?
> 
> This sounds like a missing dependency in Cygwin's Git package. I'm
> slightly surprised – the package is included in the build
> requirements, and cygport is normally pretty good at detecting runtime
> dependencies in this sort of circumstance – but I'll get it fixed as
> soon as I manage to get a new Git release out.
> 
> That's going to happen Any Day Now, although it has been Any Day Now
> for a few months at this point thanks to a variety of other life
> issues taking priority…

perhaps git.cygport needs DEPS_PATH="/usr/libexec/git-core" or something 
like that (so that executables files in that directory are included in 
the automatic dependency check)

[1] https://cygwin.github.io/cygport/pkg_info_cygpart.html#DEPS_PATH


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