Emerge: Plotting build dependencies graph, emerge -k/-j

Sascha L. Teichmann sascha.teichmann at intevation.de
Tue Jul 20 15:10:38 CEST 2010


Hi Ralf,

Am 20.07.2010 12:59, schrieb Ralf Habacker:
> Sascha L. Teichmann schrieb:
>> Hi together,
>>
>> some of you may heard me talking about the "emerge -j/-k" stuff at
>> the KDE for Windows meeting here at Osnabrück/2010-06-05. Now its
>> finally there! :-)
>>
>> We've have made some improvements to emerge that allow us to set
>> it up in a more automated/unattended environment to build
>> Kontact Enterprise 5 (KDE/PIM E5).
>>   
> This looks very good.
>>   I - Plotting the build dependencies graph as a dot graph.
>> [...]
> This is a very usefull feature for dependency checking - I played 
> yesterday with this  and found immediatly two dependency issues which 
> should be solved.
> 
> 1. win32libs-bin/libxml depends on iconv, while other packages requiring 
> iconv depends on win_iconv
> 2. wget is listed as dependency for many packages. For my opinion wget 
> should only be the first dependency of virtual/base and nowhere else.

Agreed. Maybe a step further would be the assumption that virtual/base
is an implicit dependency for all package, so we don't have to model
it for each and every package?!

> 
> An issue i found while running
> 
> python bin\dependencies.py enterprise5/kdepim-e5 > kdepim-e5.dot
> 
> is that a debug line is printed at the top of the dot file  - not sure 
> yet where it came from.



More information about the Kde-windows mailing list