1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA256 |
3 |
|
4 |
On 11/03/14 09:10 PM, William Hubbs wrote: |
5 |
> On Tue, Mar 11, 2014 at 10:10:42AM -0400, Ian Stakenvicius wrote: |
6 |
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 |
7 |
>> |
8 |
>> On 10/03/14 07:30 PM, William Hubbs wrote: |
9 |
>>> All, |
10 |
>>> |
11 |
>>> for bug 373219 [1], we are working on providing a functions.sh |
12 |
>>> that does not rely on OpenRc so that people who are not using |
13 |
>>> OpenRc can completely remove it from their systems. |
14 |
>>> |
15 |
>>> I can now report that gentoo-functions has been added to the |
16 |
>>> tree. Also, I have opened a tracker [2] that explains how to |
17 |
>>> change packages that source /etc/init.d/functions.sh. They |
18 |
>>> should first check for the existence of |
19 |
>>> /lib/gentoo/functions.sh and source that. If it doesn't exist, |
20 |
>>> they should source /etc/init.d/functions.sh. Also, do not add |
21 |
>>> hard dependencies to your packages on gentoo-functions. The |
22 |
>>> goal is to add gentoo-functions to @system once it is stable. |
23 |
>>> |
24 |
>>> The quickest way to find things that will need this fix is to |
25 |
>>> rm /etc/init.d/functions.sh and file bugs against things that |
26 |
>>> break and make them block the tracker. |
27 |
>>> |
28 |
>> |
29 |
>> - From what I remember about conversations on this in the past, |
30 |
>> and hopefully vapier can confirm, the de-facto location for this |
31 |
>> script is supposed to be /etc/init.d/functions.sh. Was there a |
32 |
>> general consensus on the approval of that location change? I |
33 |
>> still think, at worst, we should ensure the gentoo-functions |
34 |
>> script installs a symlink here (possibly taking over the one |
35 |
>> installed by openrc, if openrc still installs one) |
36 |
> |
37 |
> This was discussed at length on the bug. After multiple people |
38 |
> presented arguments supporting changing this location, vapier was |
39 |
> given ample time to weigh in with reasons that we shouldn't change |
40 |
> it. He did not, so it has been changed [1]. |
41 |
> |
42 |
|
43 |
yeah.. I scanned that bug, saw his arguments, but didn't see anything |
44 |
afterwards that seemed to address his arguments (nor anything that |
45 |
specifically addressed the removal of /etc/init.d/functions.sh as the |
46 |
de-facto location). |
47 |
|
48 |
Don't get me wrong, i think it is very pertinent to install the actual |
49 |
"lib" elsewhere, but since this is still the de-facto location we |
50 |
should have a symlink. |
51 |
|
52 |
|
53 |
> No, I don't think gentoo-functions should take over the symbolic |
54 |
> link in /etc/init.d/functions.sh; that needs to stay with OpenRc. |
55 |
> My plan there is to work that into a script that prints a warning |
56 |
> message. It will stay that way until openrc-1.0. OpenRc upstream |
57 |
> uses semantic versioning [2]. This means that as long as we are at |
58 |
> 0.x we have to keep things backward compatible. |
59 |
> |
60 |
|
61 |
...why not? As you've said yourself, nothing related to openrc uses |
62 |
/etc/init.d/functions.sh; if everything else in the tree is going to |
63 |
use the new gentoo-functions "lib", why wouldn't custom end-user |
64 |
scripts too? |
65 |
|
66 |
(again, scanned the bug, didn't see anything relevant to this) |
67 |
|
68 |
>> Also, just to confirm, this new path is compatible with the |
69 |
>> einfo package used as part of Prefix, yes? Or other arrangements |
70 |
>> have been made (ie, the einfo package will be dropped from |
71 |
>> baselayout-prefix)? |
72 |
> |
73 |
> No one has said anything to me about prefix so I don't know what |
74 |
> they want to do. To be honest I would prefer that they drop einfo. |
75 |
> unless there is a good reason for them not to. |
76 |
|
77 |
This is something that should probably be managed, then, before the |
78 |
migration to gentoo-functions is completed -- anyone here from th |
79 |
prefix team, that wants to weigh in? Will gentoo-functions work in |
80 |
prefix (well enough to replace einfo)? |
81 |
|
82 |
|
83 |
-----BEGIN PGP SIGNATURE----- |
84 |
Version: GnuPG v2.0.22 (GNU/Linux) |
85 |
|
86 |
iF4EAREIAAYFAlMgXdIACgkQ2ugaI38ACPCseAD/VLbvGkzN53hx8Z0C9xOHlJxe |
87 |
VOZu39w+HQhVa5V6vGMA/A+zmmnKjMV1pqJSgCJhgClBu7Ms9QeauZKcvjeKddqx |
88 |
=Ozpu |
89 |
-----END PGP SIGNATURE----- |