Ticket #407 (new defect)
build and runtime dependencies
| Reported by: | robertc@… | Owned by: | thomas |
|---|---|---|---|
| Priority: | major | Milestone: | 0.2.8 |
| Component: | moap | Version: | TRUNK |
| Keywords: | Cc: |
Description
What would be really valuable to me is the ability to encode build and runtime dependencies for the project. I don't particularly care (at this point anyhow) about breaking them down per-release, or per-output (e.g. one tree that builds bindings in several languages, I'd be happy to list all the languages etc).
This isn't supported by DOAP at the moment, but i'm about to pig the doap-interest list to see where previous discussions about it got to.
The goal would be to be able to spider the doap files of the dependency graph, transitively, to see what the things needed [in the opinion of the developers of the project] - and check for them locally (though that is a separate layer.
Long term that should aim to reduce maintenance burdens on distros packaging my projects.
That's something I've wanted too, but it's a really big task in today's distro ecosystem.
Moap tries to improve the user experience as well by suggesting how to install missing runtime deps; see moap.util and deps/distro
That's stuff I've been thinking of extracting out to a separate project and using in some other projects I work on.
I agree with the idea of being able to express that in the .doap file somehow.