I am doing the install for the third machine, but Mint14 (not Mint 13 LTS) this time. Now a stupid hiccup.

All the preliminaries attended to with no issues. The gzipped tar file is put into the /src directory, thus I can do:

Code: Select all

~/kde4/src $ tar -xzvf calligra-latest.tar.gz

then after this has unpacked into ~/kde4/src/calligra

~/kde4/src/calligra $ ./initrepo.sh

the first line of initrepo.sh deletes the file, and that is what it does. There is no file checking, and then the only thing in directory calligra is sub-directory .git . It complains 'cannot find git'

If I follow the cmake process it cannot find CMakeLists.txt in ~/kde4/src/calligra - not suprising as the clutch of files that I see in the same directory on builds on the other two machines is not there.

I think the tar extraction process is not correct. Where have I gone wrong?

regards
Ian

You probably don't have git installed.

By the way, those are not the release tarballs -- are you sure they are what you want? Those are some random snapshot of the development repo. The release tarballs are on download.kde.org.

Sven

Sven, hi,

scummos wrote:You probably don't have git installed.

thanks, I should have got this myself. But I was fooled by the first of three recent installs.

Install 1. brand new machine. no memory of ever installing git myself, but it is there.
Install 2. old machine, has everything on it, git included
Install 2. newish machine. git not installed, hence the problem

scummos wrote:By the way, those are not the release tarballs -- are you sure they are what you want? Those are some random snapshot of the development repo. The release tarballs are on download.kde.org.

the tarball is the one referred to in the Calligra/Building document from the kde community wiki. Development Version, Option 2. This is fine, can't be so random!

Regards
Ian

Mh, okay, I think someone should change the wiki then. If you want to build the development version, you should clone the repo from anongit.kde.org using git. Those tarballs are snapshots generated for people with slow or shaky internet connections (because git clone doesn't support resuming). They don't even contain the latest dev version, you are supposed to update them after unpacking (using git pull).

Greetings!

Sven, hi,

I take your point. I was in fact looking for the easiest way out, to minimise the complexities of the operations since I was unfamiliar with git. So downloading a tarball looked the easiest way for me.

What the Calligra/Building docs say is

Code: Select all

From now on, you can run

$ git pull

to update, or if you have local changes:

$ git rebase origin/master


Note the first line. I took it that this was a job for the future and that what I got was the latest.

Such is my level of skill in these matters that I have to ask stupid questions. Here is today's.

If I do a 'git pull' then I will need to do 'cmake' then 'make install' afterwards to rebuild the changes?? I am sure the answer is 'yes' . . . . but before i do something I regret . . .

regards
Ian

Yes, exactly. git pull will only fetch the updated new source code, which needs to be compiled into new program binaries using make. Then those new binaries need to be copied to the installation directory using make install.

Running cmake again ist not required, since the makefiles generated by cmake (which are executed by make) will automatically re-run cmake if it should be required. You can do it though, it does no harm.

The git pull is actually advisable right after unpacking the tarball, because generating the tarballs is only done every once a while (it takes lots of resources) and the repo in there might not be up-to-date. But no worries, you could not have known that
As said, the better variant is to just use git clone <the git URL on the project page>.

Greetings!

@scummos For powerusers that support us with feedback/tests I recommend the tarball for a quick start, then "git pull" to update immediately (and doing this regularly). Per our policy, the "master" git branch in calligra is defined as really stable, contains reviewed changes only. I know other KDE projects treat "master" differently, it's individual decission.

@inksi If you do a 'git pull', you just need to go to the "build directory" and type "make".
Then as usual: "make install". I'll add risking that I am repeating myself:
You can add -j5 (or greater than 5) after the "make" command to compile faster (concurrently) Also note, "make install" contains the "make" step, so you can skip "make" (I often skip it). If there's some new code to compile, it will be compiled. Also if cmake has something to do, it will be automatically invoked Feel like in heaven with those goodies, believe me, there are other projects that are not so easy to build.

Wow, it actually works! updated my laptop dev machine. will do the other two just now.

best regards
Ian

jstaniek wrote:@scummos For powerusers that support us with feedback/tests I recommend the tarball for a quick start, then "git pull" to update immediately (and doing this regularly). Per our policy, the "master" git branch in calligra is defined as really stable, contains reviewed changes only. I know other KDE projects treat "master" differently, it's individual decission.

Ok, you are of course free to recommend whatever you think works best for the target audience you want to address.
My concern was to express that the snapshot tarballs are usually not the most elegant way to obtain the code, since you need git anyways and unlike with git clone, you get a slightly old version at first and then need to update that immediately. But if you had a reason to put it into the wiki like this it's fine.

Greetings!