Freeciv experience

The experience I had with Freeciv in TOS chapter 5 was very helpful.  Too bad I didn't go through it earlier this weekend however, because it is essentially the same sort of thing I've been dealing with in SugarLabs.  The guide through the Freeciv installation teaches us how complex these projects can be.  There are a ton of sources, packages, files, extensions, etc. that need to be in place in order for things to build properly.  Taking the time to make sure that you've properly added all of the required dependencies for a project is very important, and can save you a lot of time in the long run.

Some of the processes I went through in Freeciv were a bit confusing at first.  Freeciv keeps referencing "yum" to download packages, but in Ubuntu we use "apt-get".  There were also some subtle differences in package names that Freeciv referred us to, but searching for the packages in the Ubuntu Software Center allowed me to figure out which ones I needed.  Also, there were quite a few packages it asked to install that my version of Ubuntu seemed to already have in place.  

The next phase of Freeciv was "make".  Make seems to be the building of the entire Freeciv project.  Running make required us to install a c++ compiler.  The one that Freeciv referenced didn't work, but it seems that Ubuntu also already has one built in called "libstdc++6".  Generally, most of the error messages that I would get weren't always the same as the ones documented by Freeciv, but finding the solution wasn't too hard.

Once this was completed, I was expecting to feel some sort of accomplishment for gathering all of the packages/files successfully, but it seems there wasn't any sort of "Congratulations" for getting here.  Seems that the main goal of this assignment was simply to have an idea of how to successfully build a project that has a handful of dependencies.

Some Sugar-related stuff:

I've gotten all of the packages that were throwing errors previously in my jhbuild for sugar to work.  The activities seem to work properly now, and I'm able to build the project.

The next step will be getting ourselves set up with subversion this weekend, along with trying to figure out how to get started with the bug we're going to address.