Gentoo Archives: gentoo-dev

From: Christopher Head <chead@×××××.ca>
To: gentoo-dev@l.g.o
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 15:37:39
Message-Id: 88EC1ECA-EEF3-4E70-A5A6-841509EDA277@chead.ca
In Reply to: [gentoo-dev] rfc: moving default location of portage tree (was: [gentoo-project] Call for agenda items - Council meeting 2018-07-29) by Ulrich Mueller
1 On July 18, 2018 2:55:55 AM PDT, Ulrich Mueller <ulm@g.o> wrote:
2 >It was mentioned that all three directories (ebuild repository, binary
3 >packages, distfiles) have some characteristics of a cache. However, I
4 >think this is much more true for distfiles than for the other two,
5 >which cannot be easily restored to a previous state.
6
7 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.
8
9 --
10 Christopher Head

Attachments

File name MIME type
signature.asc application/pgp-signature

Replies

Subject Author
[gentoo-dev] Re: rfc: moving default location of portage tree Ulrich Mueller <ulm@g.o>