| 1 |
All, |
| 2 |
|
| 3 |
there is a significant change I want to make to the |
| 4 |
sys-process/runit ebuild to fix a couple of bugs [1] [2]. |
| 5 |
|
| 6 |
In a nutshell, we set up a default runlevel as shown in this upstream |
| 7 |
document [3] in /etc/runit/runsvdir. We rebuild it every time an upgrade |
| 8 |
happens, so this is why we are hitting those bugs. |
| 9 |
|
| 10 |
I can think of two ways to handle building the runlevels which would |
| 11 |
leave them completely user maintainable after they are built. |
| 12 |
|
| 13 |
One is to use a use flag to build them. If I do that, I would consider |
| 14 |
forcing the use flag on with an iuse default, so anyone who doesn't want |
| 15 |
the runlevels rebuilt every time would need to turn it off in make.conf |
| 16 |
or package.use. |
| 17 |
|
| 18 |
The other way is to put this setup in pkg_config, which would mean |
| 19 |
a user would need to run "emerge runit --config" to have the |
| 20 |
runlevels built. |
| 21 |
|
| 22 |
The first way means that if you decide you want the runlevels built the |
| 23 |
way we build them you would need to emerge the package. The second way |
| 24 |
means that you could just use the --config option for emerge to rebuild |
| 25 |
them any time. |
| 26 |
|
| 27 |
Does anyone have any thoughts either way? |
| 28 |
|
| 29 |
Thanks, |
| 30 |
|
| 31 |
William |
| 32 |
|
| 33 |
[1] https://bugs.gentoo.org/show_bug.cgi?id=354053 |
| 34 |
[2] https://bugs.gentoo.org/show_bug.cgi?id=409469 |
| 35 |
[3] http://smarden.org/runit/runlevels.html |
Archives