From: Vlado <v.99cygwin@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Installer names not meaningful enough
Date: Thu, 01 Dec 2016 13:25:00 -0000 [thread overview]
Message-ID: <93ce058d-79e6-a213-1b6f-1ec3438b71c4@gmail.com> (raw)
In-Reply-To: <ba495ad3-5e70-0edf-7958-24644e905963@cs.umass.edu>
On 1.12.2016 13:51, Eliot Moss wrote:
> I think that including the version of the setup program could be helpful
> - I tend
> to add it (renaming the file by hand). However, clearly we've lived
> with things this
> way for a long time ...
I disagree.
I have a script to update Cygwin. This script checks for new version of
setup, downloads, verifies signature, etc. Things would become much more
complicated with variable setup file name.
Finally: Why should I care about the exact version number of setup?
Script makes backups of the old setup files like setup.exe.0001, 0002,
..., just for a cause, but never in the past I did have to looking for
the setup with exact version number.
Vlado
--
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-01 13:25 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 [this message]
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
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=93ce058d-79e6-a213-1b6f-1ec3438b71c4@gmail.com \
--to=v.99cygwin@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).