1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA256 |
3 |
|
4 |
On 11/03/14 02:24 PM, Rich Freeman wrote: |
5 |
> On Tue, Mar 11, 2014 at 1:54 PM, Micha³ Górny <mgorny@g.o> |
6 |
> wrote: |
7 |
>> Dnia 2014-03-10, o godz. 18:30:29 William Hubbs |
8 |
>> <williamh@g.o> napisa³(a): |
9 |
>> |
10 |
>>> Also, do not add hard dependencies to your packages on |
11 |
>>> gentoo-functions. The goal is to add gentoo-functions to |
12 |
>>> @system once it is stable. |
13 |
>> |
14 |
>> Why? I'm pretty sure we were working on having more explicit |
15 |
>> deps and less @system magic. This goes exactly the opposite way. |
16 |
> |
17 |
> ++ |
18 |
> |
19 |
|
20 |
++ , it makes no sense to not explicitly depend on this, when a |
21 |
package needs it. That's one of the reasons why things that use |
22 |
functions.sh now fail when openrc wassn't installed (openrc being the |
23 |
provider, until now). |
24 |
|
25 |
|
26 |
|
27 |
> Why not install it in the same place as openrc, create a virtual, |
28 |
> and have the two block? Or move the file from openrc to the new |
29 |
> package and have openrc depend on it (probably a cleaner solution |
30 |
> if you can handle the transition)? |
31 |
|
32 |
Eww, no. This is a bash script; the C internal functions that are in |
33 |
openrc already are way better for openrc to use. However, yes, both |
34 |
of these packages should be able to be installed at the same time. |
35 |
|
36 |
(note, there was a short discussion about separating einfo/libeinfo |
37 |
into its own package and having openrc depend on it, but it was |
38 |
rejected. if -that- happened then it would make more sense to go this |
39 |
direction) |
40 |
|
41 |
|
42 |
|
43 |
-----BEGIN PGP SIGNATURE----- |
44 |
Version: GnuPG v2.0.22 (GNU/Linux) |
45 |
|
46 |
iF4EAREIAAYFAlMfX5gACgkQ2ugaI38ACPCMzgD8DFPnA1JT0BGVE9nSgsEoqoo8 |
47 |
LGl4Nb9i7Q7Rewd1yZIBAJcIWP5kI9e4Wl//+O21+O7gfl7LSHnAmYxW97zDsGfm |
48 |
=OpiU |
49 |
-----END PGP SIGNATURE----- |