Jan Simonson wrote: > BTW, why is it named KPackageKit and not kpackagekitrc as seems to be the > norm? Because upstream is using the KConfig API in a strange way (passing "KPackageKit" as the config file name explicitly). Kevin Kofler
Jan Simonson wrote: > BTW, why is it named KPackageKit and not kpackagekitrc as seems to be the > norm? Because upstream is using the KConfig API in a strange way (passing "KPackageKit" as the config file name explicitly). Kevin Kofler