When extracted the kde4.tar.gz has the original structure of ktown in the kde subdirectory. In the deps subdirectory are the dependencies packages which collide with new ones and have been renamed. In the other are dependencies which don't collide and can be put aside.

The sources of KDE4 and its dependencies are in pbslacks/builds/src or known by a link in pbpathinc. You can get them once in a repository of your choice.

Then you have a SlackBuild script for every dependency in deps or other. And the big SlackBuild for the ktown/kde4 part in kde.

I have put my qt4 SlackBuild script in https://github.com/BrunoLafleur/pbsl.../kde4/other/qt

They are part of my KDE4 set of scripts in pbslacks.

I modified my pbslacks project to have my scripts inside sub repositories in builds rather than having them in tar.gz archives. It is easier to extract my SlackBuild scripts.

2 members found this post helpful.

I'll have a look to port this qt4 script to the unofficial repository for current, if it's ok for you...
or do you prefer to adapt it yourself?

1 members found this post helpful.

I have also a compiled version of KDE4 and it's dependencies for the latest Slackware current with glibc 2.33 and elogind here

It works well with my computers.

1 members found this post helpful.

It is OK for me.

Those scripts gives a working Qt4 on my machines with the latest Slackware current which works also with my full KDE4 set of packages.

They are not perfect for the SBo standards but KDE4 is very dependent of it and compilation or runtime KDE4 breaks easily is the bundled qtwebkit is there or not, so I choose to keep the couple (qt4,qtwebkit4) together.

1 members found this post helpful.

notice that I cannot keep the script as it is (because the build system doesn't allow to build it cleanly) but I think I will have to break it into two different ones, qt4 and qt4-webkit: I don't know if this is something that you prefer to manage yourself...

I will probably not manage it myself (unless I find a clean way to separate the two packages). For uses with KDE4 or older QT4 applications, qt4 and qtwebkit4 should be together. If we forget the qtwebkit, the runtime KDE4 is totally broken and won't start the next reboot.

Just a question : do you build with sbopkg ? Or other tool ? I don't use the former.

not necessarily, but yes, sometimes.
but, to be clear, the refactoring of the script shouldn't depend on the helper application: a script that builds and installs a partial version of itself in the system and then rebuilds a different version upgrading the installed one is not allowed on SBo.

I have an idea which I will test : I can put qt and qtwebkit as 2 subdirectory of one which do the merge I need. Those 2 subdir will then be sbo compliant.

However I don't know if someone will be able to compile them without the top script.

unfortunately I don't think that's allowed too: the scripts have to be able to run autonomously...
that's why the only way I saw about it has been to build and install a qt4 package and then build and install a separate, non-overlapping, qt4-webkit package.
...but if anybody has a better idea I'm all ears.

The only way is to test if it can works.
But it is probably non idempotent if we don't delete the qtwebkit package before creating it.

Dear @BrunoLafleur,

This weekend I finished preparing a "box" (aka fresh SD-card) dedicated for KDE4 build - at least the Plasma5 free system. And I seen with great satisfaction that you put on repository and "exploded" view of the KDE4 tree.

https://github.com/BrunoLafleur/pbsl...uilds/sbo/kde4

BUT, with all respect for your hard work and no offense intended at all, I will try to replicate the KTown on my take, because I am just habituated with this structure. As there's a Chinese saying: the old horse will prefer a well known road.

However, you know what lacks on your build tree? An information on what is the build order of dependencies.

In the KTown was deps.SlackBuild which permitted me to run a rebuild of deps - there is not such thing.

So, you are kind to provide at least on a text file, the order of building of KDE4 dependencies?

This will be fantastic useful for me to create some kind of deps.SlackBuild and other.SlackBuild ...

PS. I try to do the build (one package at a time with cleanup) on a 2GB zram mounted on /tmp so would be very nice if you can point out if there are packages who needs more for building.

3 members found this post helpful.

Here you can find the order in which I compile deps, other and kde (plus some tricks) from line 336 to 435.

And here are the download part. The links are in pbpathinc or bundled in builds/src.

4 members found this post helpful.

I have modified a little my qt SlackBuild : I have put qt and qtwebkit as subdirs of qt.

The twice are SBo packages.

The above directory contains a script which combined the two and which is not SBo. I used this combined script for compiling KDE4 dependencies.

Note that qt take 2Go in tmp for compiling and qtwebkit 770 Mo.

I don't know if we can compile qtwebkit without removing the package before. I didn't test for now. I will.

4 members found this post helpful.

Also I have split the script pbcompilepost by adding pbcompilekde4.

And pbaspirecore by adding pbaspirekde4.

I have also split some include scripts.

It can help for having some other.SlackBuild and deps.SlackBuild.

qt need more than 2 Go in tmp for compiling (especially with the qtwebkit part of the combined package => 2.8 Go)

4 members found this post helpful.