On Sat, 30 Dec 2006, Linas virblis wrote:
Why do you care about this anyway? Packages constantly change (add/drop) their dependencies. The information that package foo dropped dependency on package bar does not tell you much. So what if it did? You cannot simply remove it, because other packages may still depend on it.
The depended-on packages is not a very common one and I think it is useful for the sysadmin to know that it is no longer needed.
Documenting such information is only meaningful if this affects the behavior/functionality of the package in a way that is likely to break something.
Not really, I think it is always best to document these changes. Cheers, Carlo -- Carlo U. Segre -- Professor of Physics Associate Dean for Special Projects, Graduate College Illinois Institute of Technology Voice: 312.567.3498 Fax: 312.567.3494 [EMAIL PROTECTED] http://www.iit.edu/~segre [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
