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: How to reinstall everything?
Date: Mon, 18 Jan 2021 15:48:03 -0700	[thread overview]
Message-ID: <39dca0ab-c559-6499-aec7-a616c23a3d94@SystematicSw.ab.ca> (raw)
In-Reply-To: <587070012.1721774.1610916823028@mail.yahoo.com>

On 2021-01-17 13:53, matthew patton via Cygwin wrote:
> On Sunday, January 17, 2021, 02:44:37 PM EST, Achim Gratz wrote:
>>matthew patton via Cygwin writes:
>>> can we fix setup.exe to read STDIN with '-P', like so?
>>> echo 'pkg1,pkg2,pkg3' | setup.exe -P -
> 
>> You probably forgot that setup is a Windows program.  besides, you must
>> not start it from the Cygwin that you are about to install a package into.

For years I've run Cygwin Setup from a script that:

* checks if a new version gets downloaded and verifies it;
* downloads and verifies setup.ini, checking if my nearby mirror is up and up to 
date;
* starts Task Scheduler to allow me to run elevated shut down tasks for old cron 
processes, Cygwin services, remaining detached processes;
* starts Task Manager/Details/order by Image Path to check all processes are 
gone and allow me to deal with any left;
* starts Cygwin Setup with my setup.rc parameters and any new packages to install;
* kills off interactive mintty, console and pty X, bash, and its own process.

> so Windows programs can't be written to read from STDIN? I can't think of any Unix utility that uses commas to delimit. And any Windows one that uses commas is clearly improper/wrong as well.
> If "you're not supposed to invoke setup.exe from within cygwin" were true then all the 'xargs' and 'paste' workarounds are null and void. And no, I don't automatically reach for xargs to bandaid around poorly written programs that violate 50 years of convention.

It's a Windows program with 20 years of its own history built with no 
proprietary tools! You can change it.
Remember it was only recently that Windows gained support for quoted command 
line and long args, so work arounds to allow running with argument lists from 
command.com and .bat scripts were required, and have been retained for 
compatibility with downstream usages.

Window utilities with similar requirements have each added their own unique 
option handling quirks to deal with them e.g.

	> sc <system> <command> <param>= <value>...

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

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

  reply	other threads:[~2021-01-18 22:48 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-16 19:55 Hamish McIntyre-Bhatty
2021-01-16 21:02 ` Marco Atzeri
2021-01-16 21:59   ` Hamish McIntyre-Bhatty
2021-01-21 16:00     ` Hamish McIntyre-Bhatty
2021-01-21 16:24       ` Marco Atzeri
2021-01-21 16:25         ` Hamish McIntyre-Bhatty
2021-01-17 18:23   ` matthew patton
2021-01-17 19:32     ` Brian Inglis
2021-01-17 19:44     ` Achim Gratz
2021-01-17 20:53       ` matthew patton
2021-01-18 22:48         ` Brian Inglis [this message]
2021-01-17 20:10     ` Hans-Bernhard Bröker
2021-01-21 17:44     ` Bill Stewart
2021-02-04 14:21   ` Hamish McIntyre-Bhatty
2021-02-04 15:24     ` Marco Atzeri
2021-02-04 15:25       ` Hamish McIntyre-Bhatty
  -- strict thread matches above, loose matches on Subject: below --
2020-06-26 17:47 Eliot Moss
2020-06-26 18:06 ` marco atzeri
2020-06-26 18:17 ` Brian Inglis
2020-06-27 17:39   ` 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=39dca0ab-c559-6499-aec7-a616c23a3d94@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).