ke 24. helmik. 2021 klo 21.04 Guus Sliepen (g...@debian.org) kirjoitti:
>
> On Wed, Feb 24, 2021 at 03:04:18PM +0100, Santiago Garcia Mantinan wrote:
>
> > > Looking at the debdiff, I notice that upstream considers this package
> > > as deprecated and recommends using the 'bridge' command from iproute2.
> > > Is there any plan to migrate bridge-utils-interfaces to use this?
> >
> > Well, kind of, I mean, on some of the bugs, at least on #868220, we've
> > have talked about this. And given that upstream has been inactive for
> > years... we have talked about getting the bridge setup scripts on
> > ifupdown and leave bridge-utils with just the brctl tool.
> >
> > I'm crossposting and adding Guus to the mail to see if we can agree on
> > something here, I don't think it is now the time to do it, it would be
> > for post Bullseye, but I don't have any problem in rewriting the
> > scripts to use just iproute2 and maintain those scripts under ifupdown
> > so that Guus didn't have to take care of more stuff.
>
> Moving to the bridge command from iproute2 soon would be best, however
> whether the bridge-utils package does it or ifupdown doesn't really
> matter. At this point, I think it can still be done in bridge-utils,
> migrating functionality between packages during the soft-freeze is
> probably a no-go.

To me, from a user perspective, the main advantage of using the
'bridge' command from iproute2 and of merging the functionality into
ifupdown would be to always have bridge control functionality included
with ifupdown and to harmonize the regex syntax in
/etc/network/interfaces. I've filed #982959 on that particular point.

There are probably other advantages of migrating to this e.g. from a
technical perspective, but it's not my department.

Martin-Éric

Reply via email to