public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Installer names not meaningful enough
Date: Wed, 07 Dec 2016 21:57:00 -0000	[thread overview]
Message-ID: <9d6c50f4-3759-0a45-a97c-30b031a906a0@SystematicSw.ab.ca> (raw)
In-Reply-To: <CACoZoo0zFt++CnsXjvvG1rrAd3fdv2mBd9=pZiRcd6+1VDC3Eg@mail.gmail.com>

On 2016-12-07 14:40, Erik Soderquist wrote:
> On Thu, Dec 1, 2016 at 7:18 AM, Lee Dilkie wrote:
>> I'd agree that adding "cygwin" to the setup program would be nice
>> but it's certainly not the windows "way", lots of programs use just
>> "setup.exe".
> 
> I don't recall "the Windows way" being a goal of Cygwin.
> 
>> Versioning can't be added to the file name because the setup
>> program itself isn't versioned, or at least isn't the same version
>> as the cygwin you are installing... the cygwin version come from
>> the servers...
> 
> Yes, the setup program is versioned, and will complain about being 
> outdated on its own anytime it sees a setup.ini that reports a newer 
> version of the setup program exists.
> 
> I've often wondered why the setup program doesn't include its
> version number in the name like ever other package does, for
> example: openssh-7.3p1-2.tar.xz
> 
> On my own systems, I download the setup program and check its
> version, then rename the file myself to include the version number. I
> know I would greatly appreciate the setup version number in the file
> name, and suspect this could be accomplished without breaking the
> existing scripted downloads by having setup.exe and setup_x64.exe be
> symlinks to whatever the current version is. Having the version
> number of the setup program thus available could also prevent a lot
> of duplicate downloads. I know I would look at the version number
> before downloading rather than download and then compare to what I
> have.

Use wget -N to prevent duplicate downloads when the name, date, 
and size don't change.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
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

  reply	other threads:[~2016-12-07 21:57 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 [this message]
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=9d6c50f4-3759-0a45-a97c-30b031a906a0@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).