On Thu, Jul 7, 2022 at 4:49 PM Daniel Sahlberg
<daniel.l.sahlb...@gmail.com> wrote:
> It is really strange that this e-mail is not part of the thread 
> https://lists.apache.org/thread/qf1tfohrwjrjk4qm1j1l8z11hfthlcq3. This should 
> probably be brought up with Infra. Unfortunately I don't have the original 
> e-mail so I don't have the message-id, which is probably needed when 
> discussing with them.

You know what's really weird? I can't even find the original message
in my inbox. I only have my reply, which includes the following
In-Reply-To:

In-Reply-To: 
<CAB84uBW0RTUkNj30zXFLOtT3=xbhxdarvlnuotnmbg-xqq6...@mail.gmail.com>

So, I don't know. Maybe we'll be lucky and Yasuhito has the original
email, and we'll talk to Infra about it. I hope we aren't missing
other important stuff.

> I cannot find it in the core installation of Visual Studio 2022. (I have it 
> installed in the directory 
> Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team 
> Explorer\Git\usr\bin but I'm not sure if this is an addon or if we can rely 
> on this being part of all installations).

Hmm... Well I suppose we shouldn't depend on people using MSVS anyway,
since there are other toolchains for Windows.

> The awk from ezwinports is a lot newer than the gnuwin32 version. The 
> downside is that the version number is encoded in the filename and older 
> files/versions seems to be removed, so we will have to update the version 
> number whenever new versions are uploaded. This might be ok for trunk, but 
> for release tarballs we will have a problem.
>
> For this reason, I believe the gnuwin32 version is better. At least if I can 
> succeed with the build (I'm not there yet).

Yes, this would be quite irritating.

An alternative might be to figure out where we're actually using awk
and perhaps using something else that is more common? Python? A
minimal C program? Perl? (I don't speak Perl but it's already a
dependency for the Windows build.)

Nathan

Reply via email to