unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tomas Volf <~@wolfsden.cz>
To: Ian Eure <ian@retrospec.tv>
Cc: Maxim Cournoyer <maxim.cournoyer@gmail.com>,
	 72686@debbugs.gnu.org, guix-devel <guix-devel@gnu.org>
Subject: Re: bug#72686: Impossible to remove all offload machines
Date: Sun, 15 Sep 2024 21:06:13 +0200	[thread overview]
Message-ID: <875xqwivoa.fsf@wolfsden.cz> (raw)
In-Reply-To: <87ldzt606c.fsf@meson> (Ian Eure's message of "Sat, 14 Sep 2024 20:53:22 -0700")

[-- Attachment #1: Type: text/plain, Size: 702 bytes --]


Hello,

Ian Eure <ian@retrospec.tv> writes:

> Disregard this, I continued thinking after sending the email (as one does) and
> realized that any managed file will be a link into the store -- so if the system
> is reconfigured with no build-machines or channels *and* the corresponding file
> is a store link, it should be removed; otherwise, it should remain untouched. I
> can work with this.

Will this correctly handle cases where user is managing the file using
for example extra-special-file?

I wonder whether fat-warning approach would not be better.

Tomas

-- 
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 853 bytes --]

  reply	other threads:[~2024-09-15 19:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-17 16:40 Impossible to remove all offload machines Ian Eure
2024-09-14 14:55 ` bug#72686: " Maxim Cournoyer
2024-09-15  3:24   ` Ian Eure
2024-09-15  3:53     ` Ian Eure
2024-09-15 19:06       ` Tomas Volf [this message]
2024-09-19  0:35         ` Ian Eure
2024-09-22  2:26     ` Maxim Cournoyer

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=875xqwivoa.fsf@wolfsden.cz \
    --to=~@wolfsden.cz \
    --cc=72686@debbugs.gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=ian@retrospec.tv \
    --cc=maxim.cournoyer@gmail.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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).