Am 30.06.2010 15:25, schrieb Jonas Smedegaard:
Thanks, I think I understand now: only public API should be taken into account, not all symbols embedded in the shared library.
Yes, I think you summarized it in one sentence. ;)
I agree, that d-shlibs do not fully automate dependency resolving, due to this. I do consider more of a wishlist item than a bug, however: As the long description says, d-devlibdeps only *tries* to list the development library dependencies - i.e. it is a helper tool which might need some tuning in each use case.
I am fine with lowering the severity. This bug/wishlist didn't really bother me, I just filed it because we discussed about it.
However, I think the bug title was appropriate nevertheless: d-devlibdeps only *tries* to list the development library dependencies, but it misses the point in doing so. It only suggests way more -dev packages than really necessary.
I have now lowered severity and retitled according to my understanding of this issue. Please do clarify if you disagree with the judgement - or if perhaps you feel that I still didn't properly understand your point.
No, I agree with you and believe you have understood what my initial discomfort with d-devlibdeps was all about.
- Fabian -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
