| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 28/03/12 03:04 PM, Rich Freeman wrote: |
| 5 |
> On Wed, Mar 28, 2012 at 2:53 PM, Christoph Mende |
| 6 |
> <angelos@g.o> wrote: |
| 7 |
>> |
| 8 |
>> I believe it's /var/lib/<name>. Here's what FHS says: /var/cache |
| 9 |
>> is intended for cached data from applications. Such data is |
| 10 |
>> locally generated as a result of time-consuming I/O or |
| 11 |
>> calculation. The application must be able to regenerate or |
| 12 |
>> restore the data. Unlike /var/spool, the cached files can be |
| 13 |
>> deleted without data loss. |
| 14 |
>> |
| 15 |
> |
| 16 |
> I can do rm -rf /usr/portage ; mkdir /usr/portage ; emerge --sync |
| 17 |
> and it will work just fine, I think. |
| 18 |
|
| 19 |
It does, i tried it yesterday. |
| 20 |
|
| 21 |
> |
| 22 |
> That really does point to cache. The only thing different from a |
| 23 |
> browser cache is that portage doesn't automatically refresh it. |
| 24 |
> |
| 25 |
|
| 26 |
Although, we could always make emerge do an automatic --sync if, say, |
| 27 |
/path/to/portage/profiles doesn't exist. :) |
| 28 |
|
| 29 |
-----BEGIN PGP SIGNATURE----- |
| 30 |
Version: GnuPG v2.0.17 (GNU/Linux) |
| 31 |
|
| 32 |
iF4EAREIAAYFAk9zbCwACgkQAJxUfCtlWe2abgEAl8eapp2DQOYJx6RAcl6Ei/iN |
| 33 |
9L4e7tG9maNTryI6lKMBAOEqAdgWrKWx2UJ3+g7oBNFc5G7Lu+yk3deZZFN4zBjU |
| 34 |
=sluw |
| 35 |
-----END PGP SIGNATURE----- |
Archives