From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: How to reinstall everything?
Date: Sat, 27 Jun 2020 11:39:28 -0600 [thread overview]
Message-ID: <a84dfcb7-b40f-ad7e-2f59-6f0077af61c2@SystematicSw.ab.ca> (raw)
In-Reply-To: <f37eb483-307d-2ae1-3a1f-e2120ee51584@SystematicSw.ab.ca>
On 2020-06-26 12:17, Brian Inglis wrote:
> On 2020-06-26 11:47, Eliot Moss wrote:
>> I've moved to new computer and want to install the same packages I had
>> before. Is there a way to tell setup from the command line to re-install all
>> packages from my local package directory? (Things are mostly installed, but
>> not working entirely properly, and it is tedious to go through an mouse-click
>> every item to "Reinstall"!)
> $ setup-x86/_64 -P "`ls .../*tp*%3a%2f%2f*%2f/*/release/ | sort -u`"
The previous command may miss some packages that are components of other
packages, so below are commands which produce complete lists:
installed packages:
$ awk '3 == NF {print $1}' /etc/setup/installed.db
$ sed '1d;/\s[01]$/s/\s.*$//' /etc/setup/installed.db
package directories:
$ find <local package directory>/*tp*%3a%2f%2f*%2f/*/release/*/ -type d | \
sed 's!/$!!;s!^.*/!!' | sort -u
but this may include some non-packages, as would similar approaches.
> where ... is the path to your local package directory, *tp*%3a%2f%2f*%2f should
> handle your download mirror directory, /*/ handles both noarch and x86/_64
> architecture directories, release directory contains the package name
> directories, and sort -u eliminates duplicates in noarch and x86/_64
> architecture directories.
>
> Don't forget to cp -r ~/.[a-z]*, modified /etc/ files, and rerun
> {,/usr}/{s,}bin/*config scripts.
--
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-06-27 17:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
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
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=a84dfcb7-b40f-ad7e-2f59-6f0077af61c2@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).