From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?utf-8?Q?=C3=93scar_Fuentes?= Newsgroups: gmane.emacs.devel Subject: Re: [feature/native-comp] breakage on build Date: Mon, 08 Feb 2021 00:38:16 +0100 Message-ID: <8735y7la8n.fsf@telefonica.net> References: <87lfca7lsb.fsf@russet.org.uk> <831rdy5i2r.fsf@gnu.org> <87y2g5p0q8.fsf@russet.org.uk> <87im7799s9.fsf@russet.org.uk> <83o8gzrgsi.fsf@gnu.org> <87eehv7ru1.fsf@russet.org.uk> <83ft2brebq.fsf@gnu.org> <87lfc3mvi1.fsf@telefonica.net> <834kirr2b2.fsf@gnu.org> <87a6sjmqpc.fsf@telefonica.net> <83k0rmpwca.fsf@gnu.org> <875z36mv11.fsf@telefonica.net> <874kiq42zy.fsf@russet.org.uk> <871rdum8ds.fsf@telefonica.net> <87sg69mj6m.fsf@russet.org.uk> <87o8gwlhbr.fsf@telefonica.net> <877dnjso57.fsf@russet.org.uk> <87ft27lld3.fsf@telefonica.net> <875z33mscu.fsf@russet.org.uk> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="19739"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) To: emacs-devel@gnu.org Cancel-Lock: sha1:YRmyiVTL8QWPzOxfHCkcg0SkbVY= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Feb 08 00:39:04 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l8tdw-00052i-MH for ged-emacs-devel@m.gmane-mx.org; Mon, 08 Feb 2021 00:39:04 +0100 Original-Received: from localhost ([::1]:41834 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1l8tdv-00017Q-Ol for ged-emacs-devel@m.gmane-mx.org; Sun, 07 Feb 2021 18:39:03 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58592) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1l8tdM-0000hc-Fi for emacs-devel@gnu.org; Sun, 07 Feb 2021 18:38:28 -0500 Original-Received: from ciao.gmane.io ([116.202.254.214]:59032) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1l8tdJ-0006FG-53 for emacs-devel@gnu.org; Sun, 07 Feb 2021 18:38:27 -0500 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1l8tdG-0004Dj-QU for emacs-devel@gnu.org; Mon, 08 Feb 2021 00:38:22 +0100 X-Injected-Via-Gmane: http://gmane.org/ Received-SPF: pass client-ip=116.202.254.214; envelope-from=ged-emacs-devel@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: -16 X-Spam_score: -1.7 X-Spam_bar: - X-Spam_report: (-1.7 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:264144 Archived-At: Phillip Lord writes: >>> My original though was to bundle this into the install, but having done >>> a little bit of picking, I think a better solution would be to have the >>> first run of Emacs install a package from ELPA, which would actually do >>> the msys install. >> >> This is easier said than done :-) > > Why? I think the code for an unattended install is actually in the > .github actions for msys2. The hard part is not to install MSYS2, is to manage the install action from Emacs. Ask the user, remember his decision, provide a mechanism in case he changes his mind, detect and use existing installs, decide where to install... and more. > An alternative would be to just stick a bash script onto the FTP site, > and tell people "install msys2 then run this". This is not such a bad > option. That's along the lines of what I described on a previous message, although I went to the extreme of suggesting to provide Emacs as a pacman package. Do you know that a pacman package contains a functional install? That means that once you have the MSYS2 binary package, by simply uncompressing it, adding the required dlls to mingw64/bin and zipping the contents of the mingw64 directory, you have your .zip distribution. >>> And some critical things, like git which is not available as a mingw64 >>> package; I have knocked together an mingw package for it; I have no idea >>> whether the msys2 maintainers would be interested in it. >> >> Do you have a PKGBUILD? Send me a copy and I'll look at it. > > https://github.com/phillord/MINGW-packages/tree/feature/mingw64-git/mingw-w64-git That lacks SSL/SSH and Perl dependencies for the commands that still depend on it. After looking at https://github.com/msys2/MSYS2-packages/blob/master/git/PKGBUILD I was expecting a more complex procedure. If something as simple as this works, great. Otherwise, another possibility is to install MSYS2 git (the POSIX package) and tell the users to set vc-git-program / magit-git-executable, suppossing that it works. It is slower than the native port, though.