unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: Re: Some comments on the MSYS-based build
Date: Fri, 07 Jun 2013 22:51:53 +0200	[thread overview]
Message-ID: <87d2rxr6dy.fsf@wanadoo.es> (raw)
In-Reply-To: 837gi5u0lh.fsf@gnu.org

Eli Zaretskii <eliz@gnu.org> writes:

>> >> The key word in Earnie's message is *updating*. Indeed, mingw-get-inst
>> >> is not intended for updating, only for installing.
>> >
>> > Then we shouldn't tell them to use it for installing, either.
>> 
>> Why?
>
> Because they will then use it for updating as well.

We can mention the restriction on INSTALL.MSYS and hopefully the MinGW
guys will modify the installer for disallowing updates. Furthermore,
nothing terrible happens if you accidentally reuse mingw-get-inst: just
wipe all the MinGW directory and reinstall.

mingw-get-inst makes installing mingw+msys a breeze. It is a waste to
not take advantage from it.

BTW, mingw-get-inst is the recommended method for installing MinGW:

http://mingw.org/wiki/Getting_Started

"An automated GUI first time installer tool called mingw-get-inst is
currently the preferred method of installation."




  reply	other threads:[~2013-06-07 20:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-03 18:01 Some comments on the MSYS-based build Óscar Fuentes
2013-06-03 19:33 ` Eli Zaretskii
2013-06-03 19:52   ` Óscar Fuentes
2013-06-04 16:20     ` Eli Zaretskii
2013-06-07  8:34 ` Eli Zaretskii
2013-06-07 14:13   ` Óscar Fuentes
2013-06-07 14:43     ` Eli Zaretskii
2013-06-07 15:03       ` Óscar Fuentes
2013-06-07 15:18         ` Eli Zaretskii
2013-06-07 15:25           ` Eli Zaretskii
2013-06-07 15:29           ` Óscar Fuentes
2013-06-07 19:03             ` Eli Zaretskii
2013-06-07 20:06               ` Óscar Fuentes
2013-06-07 20:28                 ` Eli Zaretskii
2013-06-07 20:51                   ` Óscar Fuentes [this message]
2013-06-08  3:39                     ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d2rxr6dy.fsf@wanadoo.es \
    --to=ofv@wanadoo.es \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).