From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: update with apt-cyg ?
Date: Sun, 6 Sep 2020 19:11:19 -0600 [thread overview]
Message-ID: <8a6a9c60-5c8a-a322-0b5e-2210be28e670@SystematicSw.ab.ca> (raw)
In-Reply-To: <20200906230010.GD19595@tik.uni-stuttgart.de>
On 2020-09-06 17:00, Ulli Horlacher wrote:
> On Sun 2020-09-06 (16:27), Brian Inglis wrote:
>> On 2020-09-06 16:11, Ulli Horlacher wrote:
>>> I need an UNIX-alike update shell script, without clicky-pointy. Is this
>>> a correct way: apt-cyg update-setup apt-cyg update apt-cyg dist-upgrade
>>> ? I have testet it that way and it LOOKS ok, but maybe I am missing
>>> something?
>>
>> Whose fork of apt-cyg are you using?
>
> Ooops... there are different versions (forks)?
>
> I am using https://github.com/kou1okada/apt-cyg from
> cygwin-portable-installer :
>
> W10dev:~: apt-cyg --version
> kou1okada/apt-cyg forked from transcode-open/apt-cyg
>
>> Please read those instructions carefully, or check the source.
>
> 2558 lines of bash script... :-}
>
>> Most do not support upgrading packages as they cannot upgrade the core
>> packages. Please look for articles about running the Cygwin Setup program
>> unattended.
>
> I have tried this first:
>
> cygstart /setup-x86_64.exe --quiet-mode
>
> But this does not upgrade my cygwin installation in my users windows home,
> but does a new installation in c:\cygwin64
Download:
$ curl -OJR https://cygwin.com/setup-x86_64.exe
OR
$ wget -N https://cygwin.com/setup-x86_64.exe
If using unattended (--quiet) mode, you have to specify everything else:
$ ./setup-x86_64 -gq -R "$rootdir" -l "$pkgdir" -s $site
otherwise try semi-attended (--package-manager) chooser-only mode:
$ ./setup-x86_64 -gM -R "$rootdir" -l "$pkgdir" -s $site
which lets you see the prompt screens and decide whether you need to change
anything.
Defaults should have been saved in /etc/setup/setup.rc and packages in
/etc/setup/installed.db the first time you installed Cygwin, so that subsequent
upgrades will use the same locations.
If your alternative package manager is not following these conventions, please
consider whether that is a safe approach if other apps are needed for upgrades,
unless your package manager uses workarounds so they are not needed.
--
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 IEC units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2020-09-07 1:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-06 22:11 Ulli Horlacher
2020-09-06 22:27 ` Brian Inglis
2020-09-06 23:00 ` Ulli Horlacher
2020-09-07 1:11 ` Brian Inglis [this message]
2020-09-07 8:18 ` Ulli Horlacher
2020-09-08 7:45 ` Ulli Horlacher
2020-09-07 16:26 ` Hans-Bernhard Bröker
2020-09-07 5:40 ` Achim Gratz
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=8a6a9c60-5c8a-a322-0b5e-2210be28e670@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).