Processing dependencies only when necessary

Enrico Weigelt weigelt at metux.de
Mon Jun 2 05:32:07 PDT 2008


* Dan Nicholson <dbn.lists at gmail.com> schrieb:

Hi folks,

> Could you have a look at bug 4738?
> 
> https://bugs.freedesktop.org/show_bug.cgi?id=4738

IMHO we should first make absolutely clear what Requires.private
actually means. 

An clear definition could be:

    "Deps that are NOT VISIBLE to the outside."

(actually this always had been my understanding of it)

According to this definition, there may be *NO* interface 
inheritance (eg. package's headers include dep's headers), and
also *NO* flags passed from the dependency. In other words: 
private dependencies have *NO* (visible) influence on the
importing package. It fixes things like missing deps in static
libs behind the scenes.

If you agree on this definition, we should: 

a) make this absolutely clear in the manual
b) revert the 0.21 change which publishes private import flags
c) cut off Requires.private processing where not needed 
   (as Mikhail suggested)
   

What do you think about this ?


cu
-- 
---------------------------------------------------------------------
 Enrico Weigelt    ==   metux IT service - http://www.metux.de/
---------------------------------------------------------------------
 Please visit the OpenSource QM Taskforce:
 	http://wiki.metux.de/public/OpenSource_QM_Taskforce
 Patches / Fixes for a lot dozens of packages in dozens of versions:
	http://patches.metux.de/
---------------------------------------------------------------------


More information about the pkg-config mailing list