SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
That was the first version of KDE I ever used. Nice to see it is quite easy to still get running. I wonder if it can be restored to full functionality with little effort given how far someone already has taken it. It may be a good option even today over the "light" qt environments, given it was a pretty complete desktop system, and the light qt environments feel as of today feel so incomplete.
That was the first version of KDE I ever used. Nice to see it is quite easy to still get running. I wonder if it can be restored to full functionality with little effort given how far someone already has taken it. It may be a good option even today over the "light" qt environments, given it was a pretty complete desktop system, and the light qt environments feel as of today feel so incomplete.
I'm not an expert in all these KDE and QT things, but I don't see any software conflicts.
QT1
Code:
mkdir -p build
cd build
cmake \
-DCMAKE_INSTALL_PREFIX=/usr \
-DCMAKE_INSTALL_LIBDIR=/usr/lib${LIBDIRSUFFIX} \
-DCMAKE_INSTALL_MANDIR=/usr/man \
-DCMAKE_BUILD_TYPE=Release ..
make
make install/strip DESTDIR=$PKG
cd ..
Ah, this brings back memories, thanks lancsuk! So, can we definitely say that it can coexist with the other stuff in Slackware? If so I might give it a try when I have the time.
I think you should submit it to slackbuilds.org as well, it would be a wonderful addition .
I always liked that layout. The FHS reserves /opt for local admin use, but I don't see why packaged products like this couldn't go under /usr/opt/kde-1.1 or similar.
I'm not sure, but I guess slackbuilds.org won't accept git master-tarballs.
I'm not staff at SBo, but I've found they will accept things as long as it's a tarball and you have a host for the files. For instance, if you compress the needed git pull and have the script use that tarball (which you would host the download), they generally accept it as-is. If the script is building directly from git, that is what is frowned upon, and not generally accepted, as all scripts should build without net access.
Anyway, congrats snuk, you always find the wacky projects to tackle, reminding us how old we (and kde) are
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.