On Fr, 15 Feb 2008, Richard Hartmann wrote:
There is only one way to really find that out, but which would not be feasible
without automation. A parser that goes through all packages, looks for
includes
and saves that information into a directed graph. With some visualisation, it
would be
Richard Hartmann [EMAIL PROTECTED] wrote:
On Feb 13, 2008 10:00 PM, Frank Küster [EMAIL PROTECTED] wrote:
Richard Hartmann [EMAIL PROTECTED] wrote:
No, there are no broken Depends. There are broken dependencies, but
Depends is not the right level in nearly all cases; rather Suggests or
On Fri, Feb 15, 2008 at 7:51 PM, Frank Küster [EMAIL PROTECTED] wrote:
Why do you disagree? Just because you had some feeling about what
Depends means, but were not aware of the policy definition? Or do you
have reasons which are still valid after that citation?
Indeed, I had a different
Richard Hartmann [EMAIL PROTECTED] wrote:
Catching all those reports in one place sounds like a good idea. An
overview of how bad this is could help.
The purpose was rather to get an overview about how hard it would be to
fix all or most of them.
But if you can not resolve those dependencies
On Feb 13, 2008 10:00 PM, Frank Küster [EMAIL PROTECTED] wrote:
Richard Hartmann [EMAIL PROTECTED] wrote:
No, there are no broken Depends. There are broken dependencies, but
Depends is not the right level in nearly all cases; rather Suggests or
Recommends. That is because it is always only
Thanks for the retitle. I re-sent the report after messing up my first
submit, screwing up the topic, in turn.
Catching all those reports in one place sounds like a good idea. An
overview of how bad this is could help.
But if you can not resolve those dependencies without one large
package, that
6 matches
Mail list logo
