1 |
There are several reasons why portage, neither the tree nor (especially |
2 |
not) the distfiles should reside in /usr. |
3 |
|
4 |
/var is expected to be heavily written and read from, as it is the case |
5 |
with the portage tree. |
6 |
|
7 |
It's possibly subject to fragmentation and small file sizes and heavy |
8 |
changes, which is usually accounted for my choosing an appropriate |
9 |
filesystem and configuring it accordingly. |
10 |
|
11 |
/usr is expected to be a static directory with mostly read access and |
12 |
few to no changes on a running system. |
13 |
|
14 |
This issue seems to have been ignored for a long time. When I asked |
15 |
about it, I met two types of responses: |
16 |
|
17 |
a) Those who thought about it and agreed, that portage should be moved |
18 |
b) Those who replied "deal with it" |
19 |
|
20 |
If you can think of good counter arguement which *logically* supports |
21 |
that portage should by default reside in /usr (including the distfiles |
22 |
and everything else variable) please tell us. If not, please refrain |
23 |
from logically irrelevant statements such as the above, "you can always |
24 |
do <insert some random workarround here>" or similar ones. |
25 |
|
26 |
If you have further arguments to support my point, I'd also welcome them |
27 |
to the discussion, |
28 |
|
29 |
I expect 90% or more of the real arguments to support my point. |
30 |
|
31 |
I've also heard rumours that such an outcome has already been there in |
32 |
the past, yet, gentoo developers ignored it and kept portage in /usr for |
33 |
unknown and most likely unlogical reasons. I believe these rumours. |
34 |
|
35 |
If again, the logical conclusion will be that portage should be moved |
36 |
but it is not acted upon but logic is ignored, please ask yourself what |
37 |
kind of distribution we are. |
38 |
|
39 |
"It is a community built around a distribution which is driven by |
40 |
more than 300 developers and thousands of users. " |
41 |
|
42 |
|
43 |
regards, MD |