K3b3 why have to search for KDE and Qt dendencies?[soleved]
K3b3 why have to search for KDE and Qt dendencies?[soleved]
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.....
Last edited by joeham on 27. Sep 2009, 01:05, edited 1 time in total.
Re: K3b3 - why did I have to search for KDE and Qt dendencies?
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.
FIN
Re: K3b3 - why did I have to search for KDE and Qt dendencies?
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...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.
Re: K3b3 - why did I have to search for KDE and Qt dendencies?
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]
I thought it was a slackware thing. So far so good with Salixos.