From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from m0.truegem.net (m0.truegem.net [69.55.228.47]) by sourceware.org (Postfix) with ESMTPS id 26E233858D28 for ; Fri, 4 Feb 2022 08:14:11 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 26E233858D28 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=maxrnd.com Authentication-Results: sourceware.org; spf=none smtp.mailfrom=maxrnd.com Received: (from daemon@localhost) by m0.truegem.net (8.12.11/8.12.11) id 2148EAhC051044 for ; Fri, 4 Feb 2022 00:14:10 -0800 (PST) (envelope-from mark@maxrnd.com) Received: from 162-235-43-67.lightspeed.irvnca.sbcglobal.net(162.235.43.67), claiming to be "[192.168.1.100]" via SMTP by m0.truegem.net, id smtpdROxcyT; Fri Feb 4 00:14:01 2022 Subject: Re: Go or Rust Packages? To: Cygwin-Apps References: <20220201212221.2ymlhw7jktoymsws@lucy.dinwoodie.org> <9f6fffbb-499e-386f-a7a7-b5f65c6723cb@SystematicSw.ab.ca> From: Mark Geisert Message-ID: Date: Fri, 4 Feb 2022 00:14:01 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.4 MIME-Version: 1.0 In-Reply-To: <9f6fffbb-499e-386f-a7a7-b5f65c6723cb@SystematicSw.ab.ca> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, SPF_HELO_NONE, SPF_NONE, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no 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 08:14:13 -0000 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... I don't think anybody has mentioned a need for Rust on Cygwin before. That might be easier because of a simpler runtime than Go, but still a major, major project. ..mark