Page 1 of 1

K3b3 why have to search for KDE and Qt dendencies?[soleved]

Posted: 26. Sep 2009, 03:12
by joeham
Is this an oversight in Salix or is this inherited from Slackware? Normally in most distros the need for supporting library packages is handled by the package manager. Perhaps I am still too much of a Nube for Slackware.....

Re: K3b3 - why did I have to search for KDE and Qt dendencies?

Posted: 26. Sep 2009, 07:16
by stillborn
I never thought about this before, but looking into it seems like slapt-get handles deps from salix packages because we provide dep files too, but packages in slackware mirrors don't have them.

Re: K3b3 - why did I have to search for KDE and Qt dendencies?

Posted: 26. Sep 2009, 07:34
by gapan
stillborn wrote:I never thought about this before, but looking into it seems like slapt-get handles deps from salix packages because we provide dep files too, but packages in slackware mirrors don't have them.
Correct. Slackware repositories don't include dependency information as Salix repositories. Since k3b is a package which is offered through Slackware repositories, there is no dependency resolution for it. We probably need a wiki page for this...

Re: K3b3 - why did I have to search for KDE and Qt dendencies?

Posted: 26. Sep 2009, 09:07
by gapan
You might want to take a look here for a slackware repository that includes dependency information: http://www.stabellini.net/

Re: K3b3 why have to search for KDE and Qt dendencies?[soleved]

Posted: 27. Sep 2009, 01:07
by joeham
I thought it was a slackware thing. So far so good with Salixos.