LinuxQuestions.org - ==UPDATE== KDE 1.1.2 for Slackware 15.0 :-D

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - ==UPDATE== KDE 1.1.2 for Slackware 15.0 :-D (https://www.linuxquestions.org/questions/slackware-14/%3D%3Dupdate%3D%3D-kde-1-1-2-for-slackware-15-0-d-4175730997/)

==UPDATE== KDE 1.1.2 for Slackware 15.0 :-D

Just needed a small number of dependencies,

https://github.com/grandseiken/byacc
https://github.com/besser82/libxcrypt.git
https://invent.kde.org/historical/qt1.git
https://invent.kde.org/historical/kde1-kdelibs.git
https://invent.kde.org/historical/kde1-kdebase.git

Attachment 42084

If anyone would like to test, I've uploaded all my scripts to my Gitlab repo.

kde1-kdebase
kde1-kdelibs
kde1-kdegames
kde1-kdegraphics
kde1-kdemultimedia
kde1-kdenetwork
kde1-kdetoys
kde1-kdeutils

https://gitlab.com/slackernetukbuilds/snuk-kde1

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.

Quote:

Originally Posted by the3dfxdude (Post 6465426)

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 ..

# /usr/lib64

Code:

libqt1.so.1.45

# /usr/include

Code:

qt1

#usr/bin

Code:

connect*  dirview*  hello*  menu*    picture*  qdir*    showimg*  t10*  t13*  t3*  t6*  t9*      tictac*    validator*

cursor*  drawdemo*  layout*  moc-qt1*  pref*      qmag*    splitter*  t11*  t14*  t4*  t7*  table*  timestmp*  xform*

dclock*  forever*  life*    movies*  progress*  qwerty*  t1*        t12*  t2*  t5*  t8*  tetrix*  tooltip*

kde1-kdelibs

Code:

mkdir -p build

cd build

  cmake -DCMAKE_INSTALL_PREFIX='/usr' ..

  make

  make install/strip DESTDIR=$PKG

cd ..

# /usr/lib64

Code:

libjscript.so.2.0.0*  libkdecore.so.2.0.0*  libkfile.so.2.0.0*  libkhtmlw.so.2.0.0*  libkspell.so.2.0.0*

libkab.so.2.0.0*      libkdeui.so.2.0.0*    libkfm.so.2.0.0*    libkimgio.so.2.0.0*  libmediatool.so.2.0.0*

# /usr/include

Code:

/usr/include/kde1

kde1-kdebase

Code:

mkdir -p build

cd build

  cmake -DCMAKE_INSTALL_PREFIX='/usr' ..

  make

  make install/strip DESTDIR=$PKG

cd ..

#/usr/bin

Code:

kappfinder*          kcminfo*      kflame.kss1*  klock*          kslidescreen.kss1*

kappfinder_restart*  kcminput*    kfm*          kmatrix.kss1*  kslip.kss1*

kattraction.kss1*    kcmkeys*      kfmclient1*    kmenuedit1*    kspace.kss1*

kaudioserver*        kcmkfm*      kfmexec*      kmorph3d.kss1*  kstart*

kbanner.kss1*        kcmkonsole1*  kfmsu*        konsole1*      kswarm.kss1*

kbat.kss1*          kcmkpanel*    kfmsu2*        kpager*        kthememgr*

kbgndwm*            kcmkwm*      kfmwarn*      kpanel*        kvt*

kblankscrn.kss1*    kcmlocale*    kfontmanager*  kpipes.kss1*    kwm*

kblob.kss1*          kcmsyssound*  kforest.kss1*  kplayaudio*    kwmcom*

kbouboule.kss1*      kcontrol*    khop.kss1*    kpolygon.kss1*  kwmsound*

kbsod.kss1*          kde*          kikbd*        kpyro.kss1*    maudio*

kcheckpass1*        kdehelp*      kioslave*      krdb1*          startkde*

kcmbell*            kdm*          klaser.kss1*  krock.kss1*    startkde1-fast*

kcmdisplay*          kdmconfig*    klines.kss1*  krootwm*        unpack*

kcmikbd*            kfind1*      klissie.kss1*  kscience.kss1*

# /usr/bin/cgi-bin

Code:

helpindex*

For some reason I wasn't able to build kdelibs and kdebase with custom cmake options.

Anyway, buid time: less than 10 minutes. :D

Wow. That's excellent.

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 :).

Quote:

Originally Posted by Ilgar (Post 6466107)

So, can we definitely say that it can coexist with the other stuff in Slackware?

IIRC, these older versions of KDE were installed under /opt on Slackware... so that's a definite possibility.

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.

Quote:

Originally Posted by rkelsen (Post 6466120)

IIRC, these older versions of KDE were installed under /opt on Slackware... so that's a definite possibility.

Still testing, but I created a testing branch and did some changes.

QT1 install PATH to

Code:

/usr/lib64/qt1

KDE1 install PATH to

Code:

/opt/kde1

Quote:

Originally Posted by Ilgar (Post 6466107)

I think you should submit it to slackbuilds.org as well, it would be a wonderful addition :).

I'm not sure, but I guess slackbuilds.org won't accept git master-tarballs.

Quote:

Originally Posted by lancsuk (Post 6466937)

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 ;)

Quote:

Originally Posted by jloco (Post 6466942)

Anyway, congrats snuk, you always find the wacky projects to tackle, reminding us how old we (and kde) are ;)

wacky is the new discreet.:D

Hi,

It is great to test such software but what is the purpose beyond testing, ergo to be included in slackbuilds.

You need a maintainer full time to just update the system.