1 |
Ulrich Mueller posted on Wed, 19 Dec 2012 14:43:56 +0100 as excerpted: |
2 |
|
3 |
>>>>>> On Wed, 19 Dec 2012, Diego Elio Pettenò wrote: |
4 |
> |
5 |
>> On 19/12/2012 13:44, Marc Schiffbauer wrote: |
6 |
>>> I would suggest /var/portage ... |
7 |
> |
8 |
>> Seriously, mine is going to be a huge veto here with as much power I |
9 |
>> can put. |
10 |
> |
11 |
> Why? The portage tree is of central importance for Gentoo, so IMHO a |
12 |
> second-level directory would be acceptable for it. Besides, it currently |
13 |
> is in /usr/portage, so it wouldn't be new but would only move from /usr |
14 |
> to /var. |
15 |
> |
16 |
>> There is a _reason_ why stuff is added to /var/lib instead of having |
17 |
> |
18 |
>> /var/postgres /var/mysql /var/foobar /var/wtf /var/wth /var/imtired |
19 |
> |
20 |
>> ... |
21 |
> |
22 |
> I don't understand how this is related to the discussion. None of the |
23 |
> above have any relevance for Gentoo that would be comparable to Portage. |
24 |
|
25 |
Seriously, people, we're talking about a user-level default, not |
26 |
something there's no user-level way to change. A ... |
27 |
|
28 |
>> huge veto here with as much power I can put |
29 |
|
30 |
... seems rather strong for a simple default, for something already |
31 |
DESIGNED for the user to put wherever they want! |
32 |
|
33 |
|
34 |
FWIW, here, my tree's fully resolved to /usr/src/portage, but: |
35 |
|
36 |
PORTDIR=/p |
37 |
DISTDIR=${PORTDIR}/src |
38 |
PKGDIR=/m/pw |
39 |
|
40 |
/p -> /usr/src/portage |
41 |
|
42 |
/p because I wanted as short a path as possible. DISTDIR is set inside |
43 |
it, but to a customized srcdir name as makes more sense to me as well. |
44 |
My layman toplevel is inside as well, as $PORTDIR/layman. (Yes, rsync- |
45 |
exclude is set appropriately too.) |
46 |
|
47 |
/usr/src is a dedicated partition containing PORTDIR, the kernel git tree |
48 |
and a local automated kernel-patches dir (similar to /etc/portage/patches |
49 |
but for the kernel), and the system ccache. Actually, it contains a |
50 |
second system ccache as well, for the 32-bit chroot that's the build- |
51 |
image for my netbook. |
52 |
|
53 |
PKGDIR, /m/pw, is its own dedicated partition, with /mnt being a symlink |
54 |
to /m (short paths), and pw abreviating pkg-workstation. There's another |
55 |
dedicated partition, /m/nr/pn, that's the PKGDIR for my netbook's build- |
56 |
image (nr indicating netbook root, pn indicating pkg-netbook). |
57 |
|
58 |
The gentoo tree and overlays, along with DISTDIR, are common to both the |
59 |
workstation and the netbook, and directly net-downloadable, so keeping src |
60 |
aka DISTDIR and the layman tree inside PORTDIR, on the /usr/src |
61 |
partition, makes sense to me. But I keep separate PKGDIRs in dedicated |
62 |
partitions so I can have backup partitions for them, thus keeping |
63 |
installable binpkgs for both the workstation and the netbook, even if the |
64 |
working partitions get fscked. |
65 |
|
66 |
|
67 |
The point of all this being, these settings are DESIGNED to be set by the |
68 |
user, who can have an as crazy-for-others-but-makes-sense-to-the-user |
69 |
configuration as they want! |
70 |
|
71 |
Based on that, yes, the defaults have some level of symbolic importance, |
72 |
but even if they're something like |
73 |
/some/crazy/nth/level/weirdness/subdir/portage by default, it's *JUST* |
74 |
the defaults, and if users feel strongly about it at all, they can change |
75 |
them. IMO there's thus no reason to feel so strongly that one issues a... |
76 |
|
77 |
>>huge veto here with as much power I can put |
78 |
|
79 |
|
80 |
In fact, it could be argued that... |
81 |
|
82 |
/some/crazy/nth/level/weirdness/subdir/portage |
83 |
|
84 |
... *should* be the default, precisely to MAKE that point, that it's just |
85 |
a default for something intended to be set by the user. |
86 |
|
87 |
Not that /I'd/ argue for it, especially since the gentoo way is |
88 |
customizable configuration but sane "just works" defaults where possible |
89 |
and I'd hardly call that sane, but it /would/ make the point. |
90 |
|
91 |
|
92 |
Anyway, yes, getting the default out of /usr/portage into /var somewhere |
93 |
seems reasonable, and if I were to choose, I'd choose |
94 |
/var/cache/portage as that seems to me to be the clearest labeled intent, |
95 |
but it's a default INTENDED to be set to something else, should a user |
96 |
feel strongly about it, and as such, the default really isn't that big of |
97 |
a deal. Yes let's move it into /var, but /var/db/portage vs. |
98 |
/var/cache/portage vs. /var/portage ... if people have strong feelings |
99 |
about it, they'll move it anyway, so /whatever/ the default, even |
100 |
something as insane as the path suggested to make the point above, it's |
101 |
simply not worth having a coronary (or incinerating opposition with a |
102 |
flaming stare) over. |
103 |
|
104 |
-- |
105 |
Duncan - List replies preferred. No HTML msgs. |
106 |
"Every nonfree program has a lord, a master -- |
107 |
and if you use the program, he is your master." Richard Stallman |