On Wed Jul 30 21:27 -0400, David Walser wrote: > And the deps will only be correct at package creation time then. It's not > maintainable. The way devel things are packages keeps getting shifted around.
If there's an effective, fairly consistent policy in place (and the maintainers actually know what's going on and coordinate with each other), that's not really a problem. Perhaps that's why the debian style works: how many packages is a typical deb maintainer responsible for (by typical, I'll use the median)? If it's more than a tenth of the corresponding metric for mdk then I'll perform any public humiliation(s) this list requests and post [a link to] the video of it. It's an admitted fact that there are several packages where the maintainer essentially knows nothing about what's inside; what he knows is the minimum required to get some other package working. To my mind, *that* is the root problem; auto-dependencies are at best a bandage on the problem. I prefer to actually solve it at the root level. -- Levi Ramsey [EMAIL PROTECTED] [EMAIL PROTECTED] Take due notice and govern yourselves accordingly. Currently playing: Rush - Presto - Chain Lightning Linux 2.4.21-3mdk 03:59:00 up 4 days, 6:46, 8 users, load average: 0.08, 0.13, 0.06
