Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
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
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
|
DetailsI 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
Jason, can you give us some hint when to expect namcap 2.0 to be released? ;-)
@Jason: I'm very sorry, don't know how could I forget that. (/me scratches his head)