From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.kundenserver.de (mout.kundenserver.de [217.72.192.74]) by sourceware.org (Postfix) with ESMTPS id 148893858D20 for ; Fri, 4 Feb 2022 09:12:55 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 148893858D20 Authentication-Results: sourceware.org; dmarc=fail (p=none dis=none) header.from=cygwin.com Authentication-Results: sourceware.org; spf=fail smtp.mailfrom=cygwin.com Received: from calimero.vinschen.de ([24.134.7.25]) by mrelayeu.kundenserver.de (mreue106 [212.227.15.183]) with ESMTPSA (Nemesis) id 1N6t3Z-1m9Co517GB-018LsJ for ; Fri, 04 Feb 2022 10:12:54 +0100 Received: by calimero.vinschen.de (Postfix, from userid 500) id 377D6A80CE4; Fri, 4 Feb 2022 10:12:53 +0100 (CET) Date: Fri, 4 Feb 2022 10:12:53 +0100 From: Corinna Vinschen To: cygwin-apps@cygwin.com Subject: Re: Go or Rust Packages? Message-ID: Reply-To: cygwin-apps@cygwin.com Mail-Followup-To: cygwin-apps@cygwin.com References: <20220201212221.2ymlhw7jktoymsws@lucy.dinwoodie.org> <9f6fffbb-499e-386f-a7a7-b5f65c6723cb@SystematicSw.ab.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Provags-ID: V03:K1:uyYVWBouj1YO4xSRF9Ypn253V8lnp8yvfklu31//72lu8mXXX2e UJcXMs0AhbmhJCq0gllgstHMlcDWhXzvBF6ghiOFgKh2OINkMUHHPDSQydxI0tep/twhGsk WhgojzrCvpdjGygXd2uVLqpIM/W8kUhdDCfHCDXu3Nlh5D0soFO7IMeN+kLvbiIfy3uMvLX eu7pEHUBsIZXhpOT/z7vg== X-UI-Out-Filterresults: notjunk:1;V03:K0:Y9zzXvVGOx4=:JetV7LlLvIIsPpFEXclqbf xxKzKP+hbvuBSVuPCb7LiUb7e6bV00gVD9MOAywvl6T27wR2dPWCKuKg5Rx4rt+Pvog3Vy3AQ ZyHaI8qxWkw5Q94do9k8y5ub48GN2WFEn0Fpnc++8pLXVpX9PDaKXqtXkRYSedLS/jZMQhCtr qDVxflUNRDu0TinHpjQo5B7FGokbUQqfK9JZAAHDyT0z7eG2Y9tfue8xdCuTmcjHWv1XgrBDX dZyOFUxH8UjvPby/Wt+Pffd+TP+v6YyvJb2PGrYHGGivgfwEEMQGWpcaYNzVSLzIhUov6y5aC LWDrXka11FTloI+d4FW8pLy3IU6pQS+TcYwoEES5Oh/JuocKgNntl2QoLYGY7jHGcDbQ8xTH2 iNnLnSmFntRmIAaG9nmFaZ/i0pL7D+XyPVX8LQwp7YGF7UpzVPvo5IA4GW8YJEsu+9ZeWOGe4 WoZCHwLoDcm4LHPZhsSNUgaI+7AxMK89ZHqovKW7nCmje0nwI3jll+ZfvYT+RmgJhA0qJFR8q WsIGnSmY7A5Nh63KXjVgNfZI4oypE7SodKlOjQAuBfDnZBxM4xDMuaYI3QYt0puNC5RKqStMN dQdBOtIpoRcReljPuyCrB8GXp6Ge/G0rGjaPWFfBMv4JzXdPRnsYgQJxe2MCJqK+EMmaDIrxF yzq9r2vyAE+qfbXfHmQZ3QK9rbplBvSUm195yoTbtQwJyqEHdnDylQOkRd1cjzyloEDfyd2NW u0id8wzpWfwQzq5D X-Spam-Status: No, score=-97.8 required=5.0 tests=BAYES_00, GOOD_FROM_CORINNA_CYGWIN, KAM_DMARC_NONE, KAM_DMARC_STATUS, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H5, RCVD_IN_MSPIKE_WL, SPF_FAIL, SPF_HELO_NONE, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: cygwin-apps@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Cygwin package maintainer discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Feb 2022 09:12:58 -0000 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 basis of the > > > > last version of the Ruby code, but never managed anything useful.  In > > > > that context, I expect it's time that I officially throw in the towel, > > > > and mark fzf as orphaned. > > > > > > > > The existing build still works, and I don't think there's likely to be > > > > any crass security problems or anything like that.  But there's no > > > > longer any upstream support, and I clearly don't have the capacity to > > > > properly maintain it solo. > > > > > > > > I'm not quite sure what the process is here, but I suspect it's just a > > > > case of someone with the appropriate access making an update to > > > > https://cygwin.com/cygwin-pkg-maint > > > > Anyone know of anyone trying to build Go or Rust on Cygwin? > I made some progress with Go on Cygwin a couple years ago, but had to give > up because it required more time than I could give it. I got about 1/3 of > the way through it. The last straw was its need for syscall?() and Cygwin > not having those functions (or a need for them). It was a lot of looking > for "#ifdef Windows" and usually adding "&& !defined(__CYGWIN__)". The goal > still tantalizes though... You might be better off writing a syscall layer which translates the expected syscalls into standard POSIX API calls. Cygwin could even provide that in the long run. Ages ago we discussed converting cygwin1.dll to cygwin2.dll and only export a syscall interface with any arbitrary libc on top (e. g. glibc), but that would have been a near full re-implementation of Cygwin, so we buried the idea. However, providing a syscall layer on top might be a nice extension. Corinna