From: cyg Simple <cygsimple@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Installer names not meaningful enough
Date: Thu, 15 Dec 2016 15:54:00 -0000 [thread overview]
Message-ID: <971a029b-ae1a-00d7-a934-6a6fea3db1a1@gmail.com> (raw)
In-Reply-To: <CACoZoo3bafxrYNQn9_DpqEu7aqEomxZo+M-5sZ7Q8=UGCfAGhw@mail.gmail.com>
On 12/14/2016 4:58 PM, Erik Soderquist wrote:
> On Wed, Dec 14, 2016 at 4:50 PM, cyg Simple <cygsimple@gmail.com> wrote:
>> And if we were purely *nix your argument might hold merit but this setup
>> executable provides a Windows OS based install of a Windows based
>> application set known as Cygwin.
>
> If we were purely *nix, we wouldn't be on Windows in the first place.
>
>> The name of the executable has never been a problem; why are you trying
>> to create one? There are just as many that would keep it simple and
>> leave the name as is.
>
> I don't recall anyone trying to create a problem so much as find out
> the reasoning behind the decision and ask for the setup executable
> version information to be more accessible than it currently is. At
> present, it does not appear that the cygwin pages list the current
> setup executable version at all, forcing either an aborted setup run
> when the setup executable itself reports that the setup.ini file
> indicates the currently running executable is outdated, or downloading
> *something* to see if the version of setup available for download has
> changed.
If you that concerned about it you can check the repository tags at
https://cygwin.com/git/gitweb.cgi?p=cygwin-apps/setup.git;a=tags to find
the current released version.
--
cyg Simple
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2016-12-15 15:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-01 10:52 Roberto Ríos Gallardo
2016-12-01 12:19 ` Lee Dilkie
2016-12-01 12:51 ` Eliot Moss
2016-12-01 13:25 ` Vlado
2016-12-01 13:55 ` cyg Simple
2016-12-01 16:37 ` Ian Lambert
2016-12-05 17:36 ` Stephen Paul Carrier
2016-12-05 18:35 ` Andrey Repin
2016-12-05 18:53 ` Eliot Moss
2016-12-05 19:05 ` Brian Inglis
2016-12-01 14:06 ` Buchbinder, Barry (NIH/NIAID) [E]
2016-12-07 21:40 ` Erik Soderquist
2016-12-07 21:57 ` Brian Inglis
2016-12-07 22:06 ` Erik Soderquist
2016-12-08 4:50 ` Brian Inglis
2016-12-09 11:28 ` Vlado
2016-12-14 21:18 ` Erik Soderquist
2016-12-14 21:50 ` cyg Simple
2016-12-14 21:58 ` Erik Soderquist
2016-12-15 15:54 ` cyg Simple [this message]
2016-12-06 9:12 ` Gerrit Haase
2016-12-07 9:57 ` Duncan Roe
2016-12-07 14:46 ` Ian Lambert
2016-12-07 21:25 ` Brian Inglis
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=971a029b-ae1a-00d7-a934-6a6fea3db1a1@gmail.com \
--to=cygsimple@gmail.com \
--cc=cygwin@cygwin.com \
/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.
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).