| 1 |
On Sun, 23 Nov 2014 15:25:07 -0500, Tanstaafl wrote: |
| 2 |
|
| 3 |
> > The current Gentoo policy is that maintainers cannot block other devs |
| 4 |
> > from adding support for systemd/openrc/etc to their packages if they |
| 5 |
> > lack such support. Gentoo policy does NOT require maintainers to |
| 6 |
> > support any particular init system. |
| 7 |
> > |
| 8 |
> > If you feel otherwise, I suggest you cite the policy. |
| 9 |
> |
| 10 |
> Interesting... packages don't have to support the default init system... |
| 11 |
> |
| 12 |
> Can anyone say 'can of worms'? |
| 13 |
|
| 14 |
Well, if it goes the way Rich suggests, there won't be a default init |
| 15 |
system so this won't be an issue. |
| 16 |
|
| 17 |
Gentoo is about choice, defaults are there for when you can't be bothered |
| 18 |
to make the choice yourself, which makes defaults largely irrelevant in |
| 19 |
the Gentoo way of doing things. |
| 20 |
|
| 21 |
And if the default init system does become virtual/init, will you care or |
| 22 |
even notice? It was only when installing a new system recently that I saw |
| 23 |
that the default for virtual/cron was no longer vixie-cron, yet none of |
| 24 |
my systems using vixie stopped working... |
| 25 |
|
| 26 |
The choice will always be there as long as at least one person cares |
| 27 |
enough to ensure the choice is there. |
| 28 |
|
| 29 |
|
| 30 |
-- |
| 31 |
Neil Bothwick |
| 32 |
|
| 33 |
To most people solutions mean finding the answers. But to chemists |
| 34 |
solutions are things that are still all mixed up. |
Archives