[
https://issues.apache.org/jira/browse/MYNEWT-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15856285#comment-15856285
]
ASF subversion and git services commented on MYNEWT-558:
--------------------------------------------------------
Commit 6f60a6cd0ffdcbdeeebade8803eeb4dcd5ba33bf in incubator-mynewt-newt's
branch refs/heads/develop from [~ccollins476]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-newt.git;h=6f60a6c
]
MYNEWT-558 newt - depgraph dup nodes in split tgts
> newt - depgraph should indicate soft vs. hard dependency
> --------------------------------------------------------
>
> Key: MYNEWT-558
> URL: https://issues.apache.org/jira/browse/MYNEWT-558
> Project: Mynewt
> Issue Type: Bug
> Reporter: Christopher Collins
> Assignee: Christopher Collins
> Fix For: v1_0_0_rel
>
>
> The `target dep` and `target revdep` commands only indicate package names in
> the dependency graph. It would be helpful to see what created the dependency
> in the first place. Specifically, it would be good to know if the dependency
> is "hard" (package explicitly depends on another) or "soft" (package requires
> an API; other package happens to implement that API). This is useful when
> trying to completely remove a package from a build.
> Unfortunately, this information is lost at the time dependency graphs are
> generated. Rather than use a builder's package map, dependency generation
> should operate on an intermediate form produced by the `resolve` package.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
