ReView dependencies and crackdown on ever-expanding dependencies

Registered by A. Denton on 2010-01-18

Somehow, the entire open source developer community needs to get a handle on it. It's a big problem for some of us, and I suspect other people, organizations, etc., when trying to tailor a machine for a particular use case.

The Debian policy has a a very good statement on how to categorize dependencies (http://www.debian.org/doc/debian-policy/ch-relationships.html). Unfortunately, the policy seems not to be enforced nearly enough.

In particular, the entire community should make greater use of suggestions for enhancements and recommendations regarding dependencies. That includes virtual packages that "provide" packages, and meta-packages that are similarly to be taken into account when it comes to dependency relationships.

I'm not sure how to create a process that would herd the cats, but it's what's needed. Perhaps each distribution should have a "dependency czar" to review dependencies and crackdown on ever-expanding dependencies.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
A. Denton
Direction:
Needs approval
Assignee:
None
Definition:
Discussion
Series goal:
Proposed for lucid
Implementation:
Deferred
Milestone target:
None

Related branches

Sprints

Whiteboard

A discussion is strongly recommended. Please someone start and post a comment.

[aquina] Is the issue/blueprint still relevant?

(?)

Work Items

Work items:
Discuss the matter with all assigned devs/packagers: TODO
Write a proposal/spec for all supported distributions: TODO
Propose a specification for meeting agenda (sprint): TODO
Present the proposal/spec to developers packagers: TODO

This blueprint contains Public information 
Everyone can see this information.