I'm not certain if I ever discussed this before, but the recent tcsh
update reminded me that I think the defaults should be changed a little
bit. First off, running the scripts in profile.d should IMHO be done in
csh.login to ensure it's only done once. Secondly the (optional)
cleaning up of th
Marco Atzeri writes:
> As it is written in go, you need to go back to the oldest version
> written in C and from them forward to the current version.
No you don't. Upstream opines that they already support Windows and
Linux and thusly do not need Cygwin. The details vary, but Rust climbed
up the
On 04.02.2022 16:28, Allen Hewes wrote:
-Original Message-
Welp, then the wheels came off. I am assuming that Cygwin's python-
cryptography is still at 3.3.2 b/c of this Rust issue?
Hi Allen,
it is correct. I released the last version that was still on C
It's still on C but th
On 04.02.2022 10:23, Jan Nijtmans wrote:
Op vr 4 feb. 2022 om 07:58 schreef Marco Atzeri:
As it is written in go, you need to go back to the oldest version
written in C and from them forward to the current version.
There's also a "golang" frontend for gcc. Could that be used
to bootstrap go?
> -Original Message-
> From: Cygwin-apps
> On Behalf Of Marco Atzeri
> Sent: Friday, February 4, 2022 1:52 AM
> To: cygwin-apps@cygwin.com
> Subject: Re: python-cryptography >= 3.4.0 and Rust
>
> On 03.02.2022 23:11, Allen Hewes wrote:
> > Hi @all,
> >
> > I use Cygwin pretty much like Lin
Op vr 4 feb. 2022 om 07:58 schreef Marco Atzeri:
> As it is written in go, you need to go back to the oldest version
> written in C and from them forward to the current version.
There's also a "golang" frontend for gcc. Could that be used
to bootstrap go?
Regards,
Jan Nijtmans
On Feb 4 00:14, Mark Geisert wrote:
> Brian Inglis wrote:
> > On 2022-02-02 02:44, Corinna Vinschen wrote:
> > > On Feb 1 21:22, Adam Dinwoodie wrote:
> > > > The upstream fzf package moved from Ruby to Go some time ago. I had
> > > > vague but noble intetions to try to maintain a fork on the ba
Brian Inglis wrote:
On 2022-02-02 02:44, Corinna Vinschen wrote:
On Feb 1 21:22, Adam Dinwoodie wrote:
The upstream fzf package moved from Ruby to Go some time ago. I had
vague but noble intetions to try to maintain a fork on the basis of the
last version of the Ruby code, but never managed a
