Dan Allen has written a tutorial on Konstruct, a build utility that eases the process of building KDE releases from source by downloading tarballs and collating the required compilation steps.
Thanks, nice tutorial
I've been using konstruct a couple of times and is really really easy.
Wouldn't it be nice to have a binary-only demo/release for each KDE minor version?
Mainly for Linux x86, but the same is possibile for other platforms.
Something like a tarball that goes into /opt/kde.x.y, with very few dependencies like minimum kernel, glibc and X version.
Something like Mozilla or OpenOffice for instance.
I know that package systems/manager are better, especially in production environments where security fixes may be important.
But having a demo of the whole KDE at each release could be useful (for quick bug tracking or PR for instance).
Is it something worth, possible or am I an idiot?? ;-)
Comments are welcome.
Kongratulations, it's kool.
> Wouldn't it be nice to have a binary-only demo/release for each KDE minor version?
A solution without any dependencies would be a small Live-CD, like Slax already is.
Also a live CD could be nice, and there is one already I see
I was thinking of something distro-independent that you can easily install on disk with only the latest KDE stuff
take a look at byzantine linux: here
If you install all of the dependencies for KDE, it is a lot more stuff than KDE itself. I know this because I recently did a new install of Linux. This was Linux Mostly From Scratch, so I started with only GLibc and BinUtils built from source and only the few RedHat RPMs needed to boot to the console. After that everything was installed individually either from RPM or built from source. So, I know all of the dependencies that I installed to get KDE up and running.
This would probably fit on a CD, but downloading it all as a tarball is probably out of the question.
take a look at the SLAX CDhttp://slax.linux-live.org/features.phphttp://slax.linux-live.org/installed_packages.txt
all in 170 MB
anyway can you mail me your dependency list?
A CD with all KDE packages would be of course slightly bigger.
First about the problem with "something" overwriting the PATH.
With the Xsession script produced by the KDM installation, the problem is that you shouldn't source "~/.bash/env-konstruct.sh" from: "~/.bashrc". It should be sourced from: "~/.bash_profile" (on Linux assuming that Xsession is using Bash to run itself). Note that older versions of KDM may require a link:
~/.profile -> ~/.bash_profile
This should fix the problem without having to edit the scripts. If it doesn't, it is probably caused by problems with KDM setting the PATH. KDM tries to add to the PATH and this simply doesn't work correctly. If you are properly adding: "KDEDIR/bin" to your path either in 'profile' or a 'profile.d' script then you should edit these two lines in the: "[X-*-Core]" section of your global: "kdmrc" file (not the one installed with Konstruct) to read:
But, the big question is what if you want to permanently install the new KDE.
There are two issues.
1. Konstruct installs Qt in the wrong place.
2. You need to globally set the various environment variables if you want to use KDE for all user accounts. On Linux, this should use 'profile.d' scripts.
The tutorial needs to include this since this is one of the problems that users ask about on the support lists.
I have issues with the Xsession produced by script that I would include in the tutorial, but I think that it will work even though part of it is a kludge.
I also wondered about the fonts issue. KDE only installs 3 fonts:
which will be installed in: "/opt/kde3.2.1/share/fonts/" and (on Linux at least) KDE does not use the X fonts system but now uses FontConfig. When using FontConfig to find the fonts, the various stuff in the: "startkde" script that sets the X font path is useless. All that is needed to find fonts is for the directories to be added to: ":/etc/fonts/local.conf". Add as the next to last line:
and execute as root: "fc-cache -vf".
Also, is there some reason that you are installing in: "/opt/"? rather than:
"/usr/kde-/"? It appears to me to be a bug in Konstruct that you have to edit the script to change the prefix.
> 1. Konstruct installs Qt in the wrong place.
> Also, is there some reason that you are installing in: "/opt/"? rather than:
compliance with Filesystem Hierarchy Standard?http://www.pathname.com/fhs
> It appears to me to be a bug in Konstruct that you have to edit the script to change the prefix.
from the konstruct home page:
"By default Konstruct installs to your home directory which means you don't have to possess root privileges or risk to damage your system or affect another KDE"
>> 1. Konstruct installs Qt in the wrong place.
> what's wrong?
The normal place is: /usr/local/qt/
Not having it in the standard place might cause problems. Just a minor point but if you are making a global install, it is best to put it in the correct place and there is no reason to put it somewhere else.
>> Also, is there some reason that you are installing in: "/opt/"? rather than:
> compliance with Filesystem Hierarchy Standard?
Strange, the default KDE install is not in compliance with the FHS so it would appear more logical to conform to the KDE default than the FHS. Put this is just a personal preference. The FHS is ugly and lots of stuff doesn't conform to it and I see these as an improvement.
>> It appears to me to be a bug in Konstruct that you have to edit the script >> to change the prefix.
> from the konstruct home page:
> "By default Konstruct installs to your home directory which means you don't
> have to possess root privileges or risk to damage [sic] your system or affect
> another KDE"
Are you agreeing with me? My point is that you shouldn't have to edit the script. It should be a command line paramater.
> The normal place is: /usr/local/qt/
who decided that?
> Are you agreeing with me? My point is that you shouldn't have to edit the script. It should be a command line paramater.
yes it could be, why not both
>> The normal place is: /usr/local/qt/
> who decided that?
Trolltec says that in their INSTALL file included with the source code. Actually they suggest you don't use a version, but the common KDE wisdom is that it works better with a version.
> and why?
Why did they decide on that location? or Why should you use the standard location?
You should use the standard location to avoid problems.
There is no wrong place if you have limited rights. And why do you moan about Qt? It's by far not the only supporting library installed by Konstruct.
What script? gar.conf.mk? Never heard of the "configuration file" concept?
> There is no wrong place if you have limited rights.
If you are doing a *global* install, it is presumed that you do NOT have limited rights.
> Never heard of the "configuration file" concept?
Yes, but it is still editing a file. Using the command line is easier.