15 Feb
2012
15 Feb
'12
10:49 p.m.
On Wed, 15 Feb 2012 14:12:27 -0800 (PST)
Darrell Anderson <humanreadable(a)yahoo.com> wrote:
I don't know what smb4k is. :) There is no such package in Slackware. As I use both
KDE3 and Trinity in
Slackware 13.1, which does not support either in any way, and I have the Samba related
options available in
both KControls, I am left to believe the Samba KCOntrol options are part of KDE3/Trinity.
smb4k is a common GUI samba application for KDE, for what it's worth.
It's also possible that the samba panel is installed by kde-network or some other
subpackage that
I don't have installed, which would make it part of stock KDE 3.5.10 but not of stock
kcontrol.
With that said, the Samba options discussed are part
of
the Slackware 3.5.10. Therefore I presume
those options were part of the upstream KDE
repository.
If those options are not available in a particular
distro's 3.5.10, then I presume the options
were
stripped from the upstream KDE sources.
The patches applied by Gentoo to the stock 3.5.10 are in
plain view ( kdebase-3.5-patchset-13.tar.bz2
should still be retrievable from the file repositories);
none of the four kcontrol patches appears to
strip a panel. I am now 99% certain that this panel is
supplied by smb4k, rather than kcontrol itself. Possibly those who are not seeing those options in
KDE3/Trinity KControl don't have some respective build
options enabled? The tdebase build options includes an explicit -DWITH_SAMBA option, which
defaults to
OFF. I don't know how that build option affects KControl.
Unlikely, as the configure options passed are also quite visible and there's no switch
available for
enabling samba support.
However, if this turns out to be important, the answer can undoubtedly be obtained by
examining
the source of KDE 3.5.10, making it a silly thing to argue about. :)