[csw-maintainers] [libxext_devel 0004314]: xext.pc has xextproto as requirement, but no package dependency

[Roger Håkansson]

On 2010-02-27 14:49, Dagobert Michelsen wrote:
> Hi Roger,
>
> Am 27.02.2010 um 05:56 schrieb Roger Håkansson:
>> On 2010-02-27 05:43, Mantis Bug Tracker wrote:
>>>
>>> The following issue has been SUBMITTED.
>>> ======================================================================
>>> http://www.opencsw.org/mantis/view.php?id=4314
>> ...
>>> xext.pc has xextproto as requirement but libext_devel doesn't have
>>> x11_xextproto (or xextproto whichever is the correct package) as dependency
>>> ======================================================================
>>>
>>
>> Suggestion:
>> Couldn't this kind of check be done with a checkpkg module? (No, I can't write it myself, I'm illiterate when it comes to python)
>
> The more interesting question is: If the dependency is real, why hasn't
> it been cought up during link symbol checking? I don't see much value in
> checking redundant .pc files.

Because the dependency isn't symbol based rather then on header files.
And even if there had been a lib dependency this kind of dependency 
wouldn't have been caught.

Example:
Package A have liba.so, A_devel a.pc, B libc.so which depends on 
liba.so, and B_devel b.pc which have a.pc as a requirement.
When building the packages B will have A as a required dependency and 
checkpkg will sugggest that A_devel needs A and B_devel needs B, but not 
that B_devel needs A_devel.