From: Jon Turney <jon.turney@dronecode.org.uk>
To: Bill Stewart <bstewart@iname.com>,
The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: Setup: How to automate source download for packages already installed?
Date: Mon, 27 Mar 2023 21:55:38 +0100 [thread overview]
Message-ID: <6883f8d3-2759-a255-b471-4c3b78873383@dronecode.org.uk> (raw)
In-Reply-To: <CANV9t=RJDRPfdRS5QdTvdo_HpsUzKtGuzFVXctbyjshCpHkH+Q@mail.gmail.com>
On 27/03/2023 21:18, Bill Stewart via Cygwin wrote:
> On Wed, Mar 4, 2020 at 6:32 AM Jon Turney wrote:
>
>> If a package is listed for both -x and -P, it is reinstalled, so while
>> not ideal, you might be able to achieve something like what you want
>> with 'setup -I -x "package1,package2,package3" -P
>> "package1,package2,package3"'
>>
>> An option which explicitly just installs the source for a specified
>> package might be useful.
>>
>
> It seems that
>
> --local-install -x "package[,...]" -P "package[,...]"
>
> ...no longer works to automate source download for packages already
> installed...
>
> Is there another workaround? (Or did I miss something obvious?)
Sorry, based on the previous discussion at [1] this seems to be broken
at the moment, due to '-x' being broken.
[1] https://cygwin.com/pipermail/cygwin/2023-February/252994.html
If you really need this, please try old setup versions from [2]. If you
discover which version it got broken in, and/or work out how to fix it,
please let us know.
[2] https://cygwin.com/setup/
next prev parent reply other threads:[~2023-03-27 20:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-02 18:06 Bill Stewart
2020-03-04 15:16 ` Jon Turney
2020-03-04 16:57 ` Bill Stewart
2023-03-27 20:18 ` Bill Stewart
2023-03-27 20:20 ` Bill Stewart
2023-03-27 20:55 ` Jon Turney [this message]
2023-03-28 16:55 ` Bill Stewart
2023-04-14 15:32 ` Jon Turney
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=6883f8d3-2759-a255-b471-4c3b78873383@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=bstewart@iname.com \
--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).