public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Christopher Head <chead@chead.ca>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] rfc: moving default location of portage tree (was: [gentoo-project] Call for agenda items - Council meeting 2018-07-29)
Date: Wed, 18 Jul 2018 08:37:14 -0700	[thread overview]
Message-ID: <88EC1ECA-EEF3-4E70-A5A6-841509EDA277@chead.ca> (raw)
In-Reply-To: <23375.3755.971322.887796@a1i15.kph.uni-mainz.de>

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

On July 18, 2018 2:55:55 AM PDT, Ulrich Mueller <ulm@gentoo.org> wrote:
>It was mentioned that all three directories (ebuild repository, binary
>packages, distfiles) have some characteristics of a cache. However, I
>think this is much more true for distfiles than for the other two,
>which cannot be easily restored to a previous state.

Neither can a Web browser’s cache, if the remote page has changed, yet those are still called caches. Surely a cache is something that can safely be discarded without negative impact (which, for most users, the ebuild tree can be, since for most users, getting back today’s tree rather than last week’s is not a negative impact), not something that can be restored to exactly its prior state automatically.

-- 
Christopher Head

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

  parent reply	other threads:[~2018-07-18 15:37 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <23368.25818.481969.336756@a1i15.kph.uni-mainz.de>
     [not found] ` <20180713065734.63627e6f@professor-x>
     [not found]   ` <23368.58952.48436.482420@a1i15.kph.uni-mainz.de>
     [not found]     ` <CAGfcS_=2+uDShmA=RapCnmfMCRJVOa5Z04jZFkVhejX0JrY-ow@mail.gmail.com>
     [not found]       ` <23368.64354.849449.669215@a1i15.kph.uni-mainz.de>
     [not found]         ` <CAGfcS_k2JO_MtEK4GRYzJ2Q2+LxVUEa-iKR_D_bH1EzsfNv6vg@mail.gmail.com>
     [not found]           ` <23369.2669.259722.764432@a1i15.kph.uni-mainz.de>
2018-07-18  9:55             ` [gentoo-dev] rfc: moving default location of portage tree (was: [gentoo-project] Call for agenda items - Council meeting 2018-07-29) Ulrich Mueller
2018-07-18 10:06               ` Kristian Fiskerstrand
2018-07-18 12:02               ` Rich Freeman
2018-07-18 13:30                 ` Ulrich Mueller
2018-07-18 13:56                   ` Rich Freeman
2018-07-18 15:37               ` Christopher Head [this message]
2018-07-19  7:07                 ` [gentoo-dev] Re: rfc: moving default location of portage tree Ulrich Mueller
2018-07-19 20:08               ` [gentoo-dev] rfc: moving default location of portage tree (was: [gentoo-project] Call for agenda items - Council meeting 2018-07-29) Chí-Thanh Christopher Nguyễn
2018-07-27  8:32                 ` Ulrich Mueller
2018-07-27  8:40                   ` Michał Górny
2018-07-29 19:54                     ` Matt Turner
2018-07-27 14:06                   ` William Hubbs
2018-07-27 14:20                   ` Corentin “Nado” Pazdera
2018-07-27 14:31                     ` Ulrich Mueller
2018-07-27 15:06                       ` Brian Dolbec
2018-07-29 18:56                         ` Michał Górny
2018-07-29 20:16                         ` [gentoo-dev] rfc: moving default location of portage tree Ulrich Mueller
     [not found]                       ` <CACVg971M=+VATAFBwL=i9FDh=1=d-vnqPLkMyV-EnyyBZyWAYg@mail.gmail.com>
2018-07-29 19:49                         ` [gentoo-dev] rfc: moving default location of portage tree (was: [gentoo-project] Call for agenda items - Council meeting 2018-07-29) Ulrich Mueller
2018-07-29 19:56                   ` Matt Turner
2018-07-29 20:01                     ` Rich Freeman
2018-07-29 20:04                       ` M. J. Everitt
2018-07-29 20:31                       ` Matt Turner

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=88EC1ECA-EEF3-4E70-A5A6-841509EDA277@chead.ca \
    --to=chead@chead.ca \
    --cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox