| 1 |
All, |
| 2 |
|
| 3 |
it has been suggested that gentoo's oldnet scripts be split out into |
| 4 |
their own package separate from OpenRC so that they can be developed |
| 5 |
independently. I am looking at doing this for OpenRC 0.12, which I hope |
| 6 |
to release soon. |
| 7 |
|
| 8 |
This means when you emerge or upgrade to openrc-0.12, the net.* scripts |
| 9 |
will no longer be included. I am going to call the separate package that |
| 10 |
includes these scripts gentoo-oldnet. |
| 11 |
|
| 12 |
My plan is to write a newsitem when OpenRC 0.12 is released |
| 13 |
telling users this and that they will have to emerge gentoo-oldnet to |
| 14 |
get the gentoo networking scripts or turn on the newnet (maybe I'll |
| 15 |
change this to net) use flag to get OpenRC's network scripts installed |
| 16 |
and put ewarns in the ebuild if this use flag is turned off. |
| 17 |
|
| 18 |
I feel that a newsitem and ewarns in the OpenRC ebuild cover live |
| 19 |
systems well. In a nutshell, users should pay attention to their news |
| 20 |
items and ewarns. |
| 21 |
|
| 22 |
On the other hand, some are suggesting that I should add a runtime |
| 23 |
dependency to OpenRC so that it pulls in gentoo-oldnet. Since OpenRC |
| 24 |
doesn't need gentoo-oldnet in order to run, I feel like this would be |
| 25 |
abusing dependencies. |
| 26 |
|
| 27 |
Does anyone have any thoughts? |
| 28 |
|
| 29 |
William |
Archives