> Hi, > > I am the maintenair of k3b. Could you please explain what's the rationale of splitting k3b in several packages? Seems that k3b libraries are used only by k3b itself, and none of the k3b packages is architecture-independent. Isn't it better to put everything in a single package?