Hi, El 31 de març de 2012 12:26, Aurelien Jarno <aurel...@aurel32.net> ha escrit: > Given lm-sensors is completely useless on non Linux-kernel, I don't > really see the point. The package is kept on non-Linux architectures > just to avoid removing the build-deps in dozens of packages, to add it > later when either support for other kernels is added to lm-sensors or > when the non-Linux kernels start to provide access to sensors via their > /sys compatibility layer.
I'm afraid I don't understand your point. You're basically saying that either [1] or [2] may happen, and that if [1] happens, then the dependency needs to be removed, if [2] happens, then the dependency needs to be removed, and until either of [1] or [2] happen, the dependency needs to be removed anyway. I.e. you're saying the dependency needs to be removed no matter if/when [1] or [2] happen. Additionally, there's [3] which is not something that can happen, but a decision that has been discarded. If you apply solution [3], then of course the situation is different, but you didn't say that you're taking [3] into consideration. I can't make any sense of it. But maybe I'm just obtuse today. Is there someone else who understands this reasoning? [1] someone ports lm-sensors to kfreebsd [2] kfreebsd adds compatibility extensions to make lm-sensors work [3] remove the package until it works (alongside all its dependencies) -- Robert Millan -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caofdtxopxo9kb8dur8vhaeek+sxmkf1doektcisisosdwzo...@mail.gmail.com
