Le 08/05/2012 09:40, Christian Hammers a écrit : > It seems the best if both quagga and babeld add a Conflict: against each other > as it does not make much sense to have both packages installed, or?
As far as I understand it, Quagga's babeld is a fork of Juliusz Chroboczek's, and I guess from [1] that Juliusz will continue to work on babeld on his own. I guess Juliusz's changes will be merged into Quagga, but I cannot tell for the other way. Besides, I guess the release schedules of both projects are different, so it might happen that both (latest released) versions of the daemon are different at some point. I don't know much about Quagga. Isn't it possible to use it with pristine babeld? Isn't it possible to e.g. have some interfaces managed by quagga and others by plain pristine babeld (not under control of quagga)? Having both packages installed makes sense to me, and my opinion is that quagga should install its files in a way that it does not conflict with babeld... and it is almost done (babeld binary in /usr/lib/quagga), except for the manpage. What about renaming it to e.g. quagga-babeld? [1] http://article.gmane.org/gmane.network.quagga.user/12500 Cheers, -- Stéphane -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org