From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org, guix-sysadmin@gnu.org
Subject: Re: Cache eviction policy of ‘guix publish’
Date: Mon, 24 Jul 2017 16:07:15 +0200 [thread overview]
Message-ID: <87eft6kjxo.fsf@gnu.org> (raw)
In-Reply-To: <87poctkez7.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Fri, 21 Jul 2017 17:05:16 +0200")
ludo@gnu.org (Ludovic Courtès) skribis:
> Mark H Weaver <mhw@netris.org> skribis:
>
>> ludo@gnu.org (Ludovic Courtès) writes:
>>
>>> Mark H Weaver <mhw@netris.org> skribis:
>>>
>>>> How about simply adding an option to 'guix publish' that prevents any
>>>> NAR/NARINFO from being expired from the cache as long as the
>>>> corresponding item is present in the store? It could be called
>>>> something like --never-expire-valid-store-items.
>>>>
>>>> More concretely, at the point in the code where a cache item is expired
>>>> in the current code, insert an additional check: if the
>>>> --never-expire-valid-store-items option is enabled and the corresponding
>>>> store path is still valid, then do not expire it.
>>>>
>>>> What do you think?
>>>
>>> Good idea. The patch below implements this policy. I’m tempted to just
>>> make that policy the default and not even add a command-line option to
>>> switch to the current policy. WDYT?
>>
>> Sure, sounds good to me.
>
> Pushed as c95644f0172ba87822ee7ecee3d2743ebd2c84bc.
>
> I’ll update ‘guix publish’ on hydra.gnu.org sometime next week if nobody
> beats me at it.
Done!
Ludo’.
prev parent reply other threads:[~2017-07-24 14:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87pocwmakv.fsf@gnu.org>
[not found] ` <87d18vkb7q.fsf@netris.org>
[not found] ` <8760enur76.fsf@gnu.org>
[not found] ` <87a83yex52.fsf@netris.org>
2017-07-20 21:28 ` Cache eviction policy of ‘guix publish’ Ludovic Courtès
2017-07-21 0:28 ` Mark H Weaver
2017-07-21 15:05 ` Ludovic Courtès
2017-07-24 14:07 ` Ludovic Courtès [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=87eft6kjxo.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=guix-sysadmin@gnu.org \
--cc=mhw@netris.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.