Hi, Bernhard R. Link: > Resolving dependencies is a hard and complex task. In general it will > not even have a unique solution. And virtual packages, alternatives > and versioned depends needs more complexity (including backtracking > to find solutions) than most tools can do. > We're not talking about the general case here, though. > As long as only a small number of packages have the wrong priority, > starting with that set and pulling the rest in via dependencies is > likely to not run into any ugly problems. So simple algorithms have > a chance. > I'm not saying that we should immediately replace Required and Important priorities with two metapackages (which would depend on every top-level package that's currently marked as such). That'd be too complex for simple tools like debootstrap. What I am saying is that if package A is Important / Required and has a simple dependency on B, then (absent any Pre-Depends) the priority of B is not relevant any more and thus doesn't need to be overridden. The rest should be dealt with by using the priority in the package, not a centrally-maintained override file. -- -- Matthias Urlichs
Attachment:
signature.asc
Description: Digital signature