1 |
Zac Medico wrote: |
2 |
|
3 |
> On 04/10/2012 07:28 PM, Steven J Long wrote: |
4 |
>> I suppose you could script that, but again, it just seems like a lot of |
5 |
>> bother to implement an "alternative" that doesn't actually gain anything |
6 |
>> over the traditional setup (plus making sure that partitions are mounted |
7 |
>> before udev starts.) |
8 |
> |
9 |
> At least in the case of udev, we gain from not having to maintain a fork. |
10 |
> |
11 |
"Making sure that partitions are mounted before udev starts" is a lot less |
12 |
of an ask than setting up an initramfs, and changing the way we've worked |
13 |
for years. It's what you proposed: an earlymounts init script, or patches to |
14 |
Gentoo initscripts to do the same thing. Neither involves any patches to |
15 |
udev proper, so no fork needs to be maintained. |
16 |
|
17 |
>> As for the burden of ensuring that binaries installed to /{s,}bin don't |
18 |
>> link to libs in /usr, why not just automate a QA check for that, and let |
19 |
>> developers decide whether a fix is necessary? After all, core packages |
20 |
>> that do that even when configured with prefix and execprefix = /, aren't |
21 |
>> so portable, and Gentoo has always championed "doing the right thing" wrt |
22 |
>> helping upstream fix portability issues. |
23 |
> |
24 |
> If the relevant ebuild developers really want to support that, it's fine |
25 |
> I guess. Hopefully that won't involve using static links as workarounds |
26 |
> for cross-/usr dependencies. |
27 |
|
28 |
Well I for one wouldn't like that, so no argument there: it's only for where |
29 |
the package would be definitely be considered for inclusion in a rescue- |
30 |
disk/ initramfs/ partition, like say lvm2, mount or fsck. While you might |
31 |
not always be able to access the manpages, a system admin would want at |
32 |
least the binaries available. |
33 |
|
34 |
I think it was mgorny who posted a check, which is why I brought it up. |
35 |
Perhaps an opt-in check if some variable is set, would be better? That way, |
36 |
only a maintainer who wants to mark the package as system-critical, and is |
37 |
happy to deal with linkage issues for binaries (including just deciding that |
38 |
some aren't so critical, which implies an optional exclusion variable, or |
39 |
listing binaries that should be checked) would set it, in the interests of |
40 |
overall portability and helping traditional users. |
41 |
|
42 |
If a maintainer isn't interested, or upstream don't like it (ie won't accept |
43 |
bugs with such a setup even when linkage is not the issue), there's no |
44 |
additional burden. |
45 |
|
46 |
Of course, if no developer thinks it's worth doing, the discussion is moot. |
47 |
It would seem at the least useful, if not necessary, however, if Gentoo is |
48 |
going to continue to support the traditional split /usr setup. |
49 |
|
50 |
-- |
51 |
#friendly-coders -- We're friendly, but we're not /that/ friendly ;-) |