On Mon, Jun 01, 2015 at 08:40:47AM -0700, roopa wrote: > Initial thought (a suggestion from Piotr) was to see if ifupdown2 [1] can be > packaged as an alternative to ifupdown.
Sure, if there is interest in it, go ahead!
> To that effect, I have some sample packaging changes to install ifupdown
> as an alternative. I call the alternative 'ifupdown' and the two available
> alternatives are ifupdown and ifupdown2.
[...]
> My concern today is, installing alternatives for networking.init and
> networking.default. I have not seen examples of installing alternate
> init scripts. If there are existing examples, I would love to do this
> for ifupdown as well.
I actually do not think it is a very good idea to do it this way. The
alternatives system is mainly there to select a default alternative, but
to be able to use all installed ones *concurrently*. But if ifupdown2 is
using the same state files as ifupdown, I don't think it is very wise to
mix usage of both ifupdown and ifupdown2.
> The other option is to make ifupdown2 'replace' ifupdown if people want to
> try it out.
That seems easier to me. I don't see any advantage of having both
packages installed simultaneously.
--
Met vriendelijke groet / with kind regards,
Guus Sliepen <g...@debian.org>
signature.asc
Description: Digital signature
