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:25:00 -0000	[thread overview]
Message-ID: <dcf6039e-0103-ad99-676a-5cdb65a585a4@SystematicSw.ab.ca> (raw)
In-Reply-To: <3EF08C00-39BE-4A05-898D-49CB71057FD4@yahoo.com>

On 2016-12-07 07:46, Ian Lambert wrote:
> On December 7, 2016 4:57:02 AM EST, Duncan Roe wrote:
>> On Tue, Dec 06, 2016 at 10:11:42AM +0100, Gerrit Haase wrote:
>>> 2016-12-01 11:51 GMT+01:00 Roberto Ríos Gallardo says:
>>>> Please give the installers more meaningful names. In
>>>> particular, make sure "cygwin" is part of it.
>>>> "setup-x86_64.exe" is not very obvious. A version number would
>>>> be nice too.
>>> The version is part of setup.ini in the header:
>>> # This file was automatically generated at 2016-12-05 09:43:16 UTC.
>>> #
>>> # If you edit it, your edits will be discarded next time the file is
>>> # generated.  See http://cygwin.com/setup.html for details.
>>> release: cygwin
>>> arch: x86_64
>>> setup-timestamp: 1480930996
>>> setup-version: 2.876
>>> ...
>> Where is setup.ini?
> $ locate setup.ini
> /cygwin-install/path/ftp.some.mirror/x86_64/setup.ini

More generally, without locate installed or updated, 
you can find it quickly with: 

$ grep -A1 '^last-cache$' /etc/setup/setup.rc
last-cache
        C:/cygwin-package-cache

at: 

$ ls $(cygpath $(sed '0,/^last-cache$/d;q' /etc/setup/setup.rc))/?*tp%3a%2f%2f*cygwin*%2f/x86*/setup.ini

giving: 

$ grep '^setup-version:\s' $(cygpath $(sed '0,/^last-cache$/d;q' /etc/setup/setup.rc))/?*tp%3a%2f%2f*cygwin*%2f/x86*/setup.ini
setup-version: 2.876

or: 

$ sed '/^setup-version:\s/!d;s///' $(cygpath $(sed '0,/^last-cache$/d;q' /etc/setup/setup.rc))/?*tp%3a%2f%2f*cygwin*%2f/x86*/setup.ini
2.876

Unwrap commands if required to copy and paste.

-- 
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: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
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 [this message]

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=dcf6039e-0103-ad99-676a-5cdb65a585a4@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).