gapan wrote:Ah, it's SlackBuild, not Slackbuild... Learn to use the tab key to avoid such errors.

Of course do I use the tab-key to autocomplete, so the issue is not a typo.

It isn't on the $PATH, but adding "./" as you suggested brought up the same error message.

It is:

I have tried to build a newer git using Pat's slackBuild from here , but when I run it as recommended: fakeroot git.Slackbuild 2>&1 | tee git-1.9.0-build.log I get the following error: /usr/bin/fakeroot: line 178: git.Slackbuild: command not found What am I doing wrong? Note that I have also use...

Thanks for the tip! I got the icon from here, and placed it in /usr/share/pixmaps/ as you suggested.

Things fixed now!


Edit: added screenshot

Another cosmetic bug that affects the MATE Control Centre when QT is installed:



How could this be fixed?

That did the trick - thanks a lot!

I don't mind the somewhat slower build-process - the build-PC is quite fast and I can let it do its job in the background while working on other things

Thanks also for pointing me to the very informative post on the mailing list! This setup seems somewhat "scary" to me (as I am not that experienced with building environments), so I would consider preparing all the packages in a VirtualBox VM.

Would this be a good option?

Resulting packages will always have different md5sums, as file creation times are stored inside the package and those differ every single time. I had the same thought, but as I had one package with exactly the same md5sum built on both machines while the another wasn't identical, I thought that I p...