first off i like conky - its simple
if you dont have a file called .conkyrc in your home than conky uses a default configuration out of the binary.
if you take a look at
http://conky.sourceforge.net/screenshots.html you see shots and links to .conkyrc files - grap a simple one and modify it.
by the way if you did
Code:
./configure
make
su -c make install
than you have conky installed, but not as a package, so
Code:
ls /var/log/packages | grep conky
would give you nothing.
slackbuilds are cool, but maybe a bit much for conky (?)
i would say in order to get a conkypackage for slackware (what is good because you simply can remove a pkg with removepkg <pkgname>) you do it by hand - its good practice.
because by default ./configure does this (do ./configure --help |more)
[...]
--enable-audacious enable audacious player support [default=no]
--enable-bmpx enable if you want BMPx support [default=no]
--enable-hddtemp enable if you want hddtemp support [default=yes]
--enable-mpd enable if you want MPD support [default=yes]
--enable-xmms2 enable if you want XMMS2 support [default=no]
[...]
so if you want xmms2 support you have to do
Code:
./configure --enable-xmms2
and than you do
Code:
make
make DESTDIR=/tmp/conkypkg install
than you become root and do
Code:
cd /tmp/conkpkg
makepkg conky-1.4.5-i686-1.tgz
installpkg conky-1.4.5-i686-1.tgz
you have to adjust the filenames to whatever version of conky you compile etc.
if you use some strange xwm like kde or gnome, i think you have to put a line like
into your .conkyrc ...