On sön, 2010-02-07 at 16:45 +0100, Marco d'Itri wrote: > On Mar 20, Chris Dukes <pr-iproute2-v...@pr.neotoma.org> wrote: > > > 1) I'd like to see a migration path off of vlan/vconfig sooner rather > > than later. The ip-vlan script provides that now. Because > Me too, are there any news?
Not that I'm aware of. I'd like to hear from the vlan maintainer what he thinks about the suggested solution. Maybe you have news since you tagged this bug as a blocker for deprecating the vlan (vconfig) packages? I'd like the vlan people to continue maintaining vlan related stuff even if they are merged into the iproute package. I'm not personally interested in maintaining anything related to vlan as I don't have any use for it and more importantly doesn't have any way to do testing. > This should really be fixed in time for squeeze. That would be nice. I'd also like to see ifupdown 0.7. In addition to the ifupdown maintainers being unresponsive we now also have kfreebsd - which AFAIK doesn't implement rtnetlink and noone stepping up to port ifupdown to non-iproute, I guess that is just getting more and more unlikely. An additional question to all of this is why the vlan support should be provided by iproute and not ifupdown itself? ifupdown 0.6 already has some features which requires iproute (without depending on iproute), vlan would just be another one. ifupdown 0.7 has dropped all usage of net-tools and depends on iproute. -- Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
