public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Hamish McIntyre-Bhatty <hamishmb@live.co.uk>
To: cygwin@cygwin.com
Subject: Re: How to reinstall everything?
Date: Sat, 16 Jan 2021 21:59:57 +0000	[thread overview]
Message-ID: <DB7PR02MB399658E0E8FFCA071A8698D3E7A60@DB7PR02MB3996.eurprd02.prod.outlook.com> (raw)
In-Reply-To: <9f016b30-3338-47ce-b734-36aa6a3e981d@gmail.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 1702 bytes --]

Cheers. I'll ask for these to be added to that repository and have them
attributed to you. Any particular license?

Hamish

On 16/01/2021 21:02, Marco Atzeri via Cygwin wrote:
> On 16.01.2021 20:55, Hamish McIntyre-Bhatty via Cygwin wrote:
>> In reply to Marco Atzeri:
>>
>> """
>> Some time ago I put a script here:
>> https://stackoverflow.com/questions/46829532/cygwin-save-package-selections-for-later-reinstall
>>
>>
>> """
>>
>> This has been very useful for me. Is this in a git/other repository
>> somewhere? If not, I think it might aid discovery for it to go with
>> some other useful scripts in this repository:
>> https://github.com/michaelgchu/Cygwin_Specific_Repo.
>>
>> What do you think of this idea Marco?
>>
>> Hamish McIntyre-Bhatty
>>
>
> feel free to use it. I never store anywhere other than stackoverflow.
> Attached the current version, I don't rememeber if I changed
> it in the meantime.
>
> Attached another that you can find useful
> it uses cygcheck and binutils to provide the list of first level
> packages containing the needed DLL's
>
> $ cyg-dependency.sh /usr/bin/octave-5.2.0.exe
> /usr/bin/cygwin1.dll  =>  cygwin-3.1.7-1
> /usr/bin/cygX11-6.dll  =>  libX11_6-1.7.0-1
> /usr/bin/cyggcc_s-seh-1.dll  =>  libgcc1-10.2.0-1
> /usr/bin/cygstdc++-6.dll  =>  libstdc++6-10.2.0-1
> KERNEL32.dll  =>   Windows System
>
> I found useful to avoid some screwup
>
> Regards
> Marco
>
>
> --
> Problem reports:      https://cygwin.com/problems.html
> FAQ:                  https://cygwin.com/faq/
> Documentation:        https://cygwin.com/docs.html
> Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

[-- Attachment #1.1.2: 0x87B761FE07F548D6.asc --]
[-- Type: application/pgp-keys, Size: 3235 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-01-16 22:00 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 [this message]
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
  -- 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=DB7PR02MB399658E0E8FFCA071A8698D3E7A60@DB7PR02MB3996.eurprd02.prod.outlook.com \
    --to=hamishmb@live.co.uk \
    --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).