| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 27/03/12 04:08 PM, Kent Fredric wrote: |
| 5 |
> On 28 March 2012 08:59, William Hubbs <williamh@g.o> wrote: |
| 6 |
>> What I was wanting to discuss mainly was that /usr/portage isn't |
| 7 |
>> right; I think we need to move that out of the /usr directory. |
| 8 |
>> |
| 9 |
>> I'm not sure what the new default should be, nor how the default |
| 10 |
>> should be decided. Maybe we just let Zac pick one? |
| 11 |
> |
| 12 |
> While we're talking about things that probably don't belong in |
| 13 |
> /usr/ : |
| 14 |
> |
| 15 |
> src , esp /usr/src/linux and friends. |
| 16 |
> |
| 17 |
> I know its not likely to ever change, but its always felt very |
| 18 |
> very wrong to be under /usr |
| 19 |
> |
| 20 |
> I've always sort of treated /usr as if it was this big space of |
| 21 |
> "untouchable, except by package manager", and /usr/src/linux sort |
| 22 |
> of violates that sense ( as does /usr/local/ to an extent , but |
| 23 |
> its slightly different ) |
| 24 |
> |
| 25 |
|
| 26 |
Remember that these things pre-dated package managers, though, right? |
| 27 |
(of course i'm showing my own age here..) :D |
| 28 |
|
| 29 |
To further the bikeshed: |
| 30 |
|
| 31 |
- ---Quote: FHS 2.3--- |
| 32 |
/var/cache |
| 33 |
Application cache data. Such data are locally generated as a result of |
| 34 |
time-consuming I/O or calculation. The application must be able to |
| 35 |
regenerate or restore the data. The cached files can be deleted |
| 36 |
without loss of data. |
| 37 |
|
| 38 |
..ok, I guess 'emerge --sync' is a valid regeneration method for the |
| 39 |
cache. I withdraw my objection to moving /usr/portage into /var/cache |
| 40 |
-----BEGIN PGP SIGNATURE----- |
| 41 |
Version: GnuPG v2.0.17 (GNU/Linux) |
| 42 |
|
| 43 |
iF4EAREIAAYFAk9yIfEACgkQAJxUfCtlWe0NMQEAgGugDZWZS5EfB3rn3oUOU7Vf |
| 44 |
wYgYo3Oflgd4EqzjH20BAJkk2l/dXX0yAw6NZEmB9VuSfwgbQUQe/wetoMbbc5BR |
| 45 |
=4AZd |
| 46 |
-----END PGP SIGNATURE----- |
Archives