public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: Christian Franke <Christian.Franke@t-online.de>,
	"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [PATCH setup] Ignore reinstall requests if version is not accessible
Date: Sat, 17 Dec 2022 17:00:50 +0000	[thread overview]
Message-ID: <072c7812-95f7-2b48-fef6-0c47e02642d3@dronecode.org.uk> (raw)
In-Reply-To: <0c87ef72-4fdd-073e-a379-dfc2ea7630b5@t-online.de>

On 16/12/2022 15:40, Christian Franke via Cygwin-apps wrote:
> Jon Turney wrote:
>> On 11/12/2022 15:11, Christian Franke via Cygwin-apps wrote:
>>> This prevents accidental package loss if reinstall is run from local 
>>> directory but the package is no longer cached.
>>
>> Thanks.  This seems right, so please apply.
> 
> Done.
> 
> Could you please also review "[PATCH setup] Add tooltip for Ctrl+I/R/U 
> accelerator keys" before next release?

Yes, I hadn't forgotten about that, but I think it will be a bit before 
I get back to setup...

> BTW, I have a local bash-script 'cygcache' which allows to list package 
> states ([auto]installed, cached, curr/prev/test), cleanup the cache 
> using above rules (configurable) or merge cache directories into one. 
> Still requires some polishing. If there is any interest, I could ITP it 
> next year.

There's been a few ad-hoc solutions over the years, I think, but unless 
it's built into setup somehow, it's not going to reach the majority of 
users, I think.

It's been pointed out recently that the top-level cache directory should 
probably be the release label (e.g 'cygwin') rather than the mirror URL.
(There's some historical cache layout compatibility stuff in Cygwin for 
an even older scheme, but I can't remember the details...)


      reply	other threads:[~2022-12-17 17:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-11 15:11 Christian Franke
2022-12-15 17:39 ` Jon Turney
2022-12-16 15:40   ` Christian Franke
2022-12-17 17:00     ` Jon Turney [this message]

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=072c7812-95f7-2b48-fef6-0c47e02642d3@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=Christian.Franke@t-online.de \
    --cc=cygwin-apps@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).