1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA256 |
3 |
|
4 |
On 24/04/13 12:16 PM, William Hubbs wrote: |
5 |
> All, |
6 |
> |
7 |
> it has been suggested that gentoo's oldnet scripts be split out |
8 |
> into their own package separate from OpenRC so that they can be |
9 |
> developed independently. I am looking at doing this for OpenRC |
10 |
> 0.12, which I hope to release soon. |
11 |
> |
12 |
> This means when you emerge or upgrade to openrc-0.12, the net.* |
13 |
> scripts will no longer be included. I am going to call the separate |
14 |
> package that includes these scripts gentoo-oldnet. |
15 |
> |
16 |
> My plan is to write a newsitem when OpenRC 0.12 is released |
17 |
> telling users this and that they will have to emerge gentoo-oldnet |
18 |
> to get the gentoo networking scripts or turn on the newnet (maybe |
19 |
> I'll change this to net) use flag to get OpenRC's network scripts |
20 |
> installed and put ewarns in the ebuild if this use flag is turned |
21 |
> off. |
22 |
> |
23 |
> I feel that a newsitem and ewarns in the OpenRC ebuild cover live |
24 |
> systems well. In a nutshell, users should pay attention to their |
25 |
> news items and ewarns. |
26 |
> |
27 |
> On the other hand, some are suggesting that I should add a runtime |
28 |
> dependency to OpenRC so that it pulls in gentoo-oldnet. Since |
29 |
> OpenRC doesn't need gentoo-oldnet in order to run, I feel like this |
30 |
> would be abusing dependencies. |
31 |
> |
32 |
> Does anyone have any thoughts? |
33 |
> |
34 |
> William |
35 |
> |
36 |
|
37 |
|
38 |
Current users should be able to do a -uDN and still have their |
39 |
existing systems work as-is. Whether you do this via a static |
40 |
dependency or one controlled by a use flag (and be sure use flag |
41 |
defaults would have oldnet installed by default) is up to you. |
42 |
|
43 |
It's completely understandable that openrc -the project- doesn't |
44 |
contain oldnet, but the end result on gentoo still should, by default, |
45 |
imo. |
46 |
|
47 |
|
48 |
-----BEGIN PGP SIGNATURE----- |
49 |
Version: GnuPG v2.0.19 (GNU/Linux) |
50 |
|
51 |
iF4EAREIAAYFAlF4Dy0ACgkQ2ugaI38ACPAQGwD+OEg6BV5rBEGylDr5R1cfMR80 |
52 |
oyE0Mwo4HWF/IEoTWk4A/jSvwkvz6mtx8Zuja/gzZogXVYHCVbVhARUXR195BGx2 |
53 |
=2754 |
54 |
-----END PGP SIGNATURE----- |