FS#9200 - namcap doesn't detect a dependency

Attached to Project: Arch Linux
Opened by Jaroslaw Swierczynski (swiergot) - Sunday, 13 January 2008, 19:26 GMT
Last edited by Hugo Doria (hdoria) - Saturday, 11 April 2009, 18:49 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jason Chu (jason)
Hugo Doria (hdoria)
Architecture All
Severity Low
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I have a package (kadu) which uses Qt but namcap will not detect it (and it's not like this dependency is covered indirectly). I think I know the reason. Some of kadu's dynamically loaded modules depend on kdelibs. Since kadu runs fine without kdelibs, I did not include kdelibs in depends (and namcap of course complains about it). I guess when namcap detects the Qt dependency, it takes also kdelibs into account and after complaining about missing kdelibs, it doesn't see necessary to inform about Qt which in my opinion is wrong.
This task depends upon

Closed by  Hugo Doria (hdoria)
Saturday, 11 April 2009, 18:49 GMT
Reason for closing:  Won't fix
Comment by Roman Kyrylych (Romashka) - Sunday, 13 January 2008, 19:50 GMT
Jaroslaw, could you please test it with namcap from git?
Jason, can you give us some hint when to expect namcap 2.0 to be released? ;-)
Comment by Jaroslaw Swierczynski (swiergot) - Sunday, 13 January 2008, 20:10 GMT
Hmm, was namcap 2.0 released in October? In git, after 2.0 tag, I can't see anything that could fix this bug. I'll try to fix it myself later, right now I'm chasing another bug in mkarchroot/makechrootpkg ;)
Comment by Roman Kyrylych (Romashka) - Sunday, 13 January 2008, 20:13 GMT
LOL, I've just saw that too.
@Jason: I'm very sorry, don't know how could I forget that. (/me scratches his head)
Comment by Glenn Matthys (RedShift) - Friday, 05 December 2008, 23:24 GMT
What's the status of this issue?

Loading...