Re: [Tuxmath-devel] Configuring the source code.

[David B. <dav...@gm...>]

Hi Haris,

> So the code I have downloaded is the current master right? How can I get
> hold of the "commonification" branch? And is that term technical or just a
> reference name? I would like to start development as soon as possible.

It is a remote branch of the tuxmath git repo - see:

http://book.git-scm.com/4_tracking_branches.html

If you haven't done so already, create a local git clone that supports
pushing (i.e. writing) as well as pulling, and do the same for our new
t4kcommon library:

git clone git+ssh://blu...@gi.../git/tux4kids/tuxmath.git
git clone git+ssh://blu...@gi.../git/tux4kids/t4kcommon.git

(tuxmath and tuxtype have shared a lot of similar code for some time,
and t4kcommon is our project to make this into a proper library).

First go to your t4kcommon repo and build and install the library just
as you did for tuxmath:

mkdir build
cd build
autoreconf -if ..
../configure
make
sudo make install

(you may need to add /usr/local/lib to your system's link path, which
on Debian and Ubuntu can be done by simply running "sudo ldconfig"
with no arguments.  This only needs to be done once).

Then go to your tuxmath git repo and check out the "commonification" branch:

git branch --track commonification origin/commonification
git checkout commonification

This will change the contents of your local working copy to match the
commonification branch.  Now you can build and install our latest
current version.

I would recommend that you keep reading the git book and familiarize
yourself with the "pull" and "push" operations, commits, and local
branches.  Your work flow could be something like this:

(cd to tuxmath git directory)
git checkout commonification
git pull
(work on some files with editor of choice, test your changes, etc.)
git commit -a
git push

Everyone in the project has privileges to push commits into the repo,
but try not to push anything that breaks stuff.  Start out with minor,
innocuous stuff.  Of course, feel free to do whatever you want on your
own machine.  Local branches are good for trying out more radical
ideas, and you can simply delete the branch whenever you like.  It is
considered good git practice to do development in local branches, and
then use "merge" or "rebase" to move your work into the tree.

You really need to get a feel for git before you can do much with the project.

Best,

David