Originally Posted by elishac
I've told you I'm a beginner, I have no idea what I'm doing.
The general rule for installing anything on Linux is to get it from the repositories associated with your distribution.
On rare occasions, what you want isn't there. On rarer occasions, it is there but there is some good reason for getting it elsewhere (such as direct from the project supporting the software you want). But unless you have a good understanding of why you are getting a specific piece of software from somewhere other than the repositories, you're probably making a mistake.
The apt-get system provides command line access to the repositories. The commands you quoted in your first post get (from the repositories) several packages that are either needed by codeblocks itself or that you would need in order to use codeblocks.
The Synaptic program is a GUI front end for the same repository system accessed by apt-get. In cases where you don't know exactly what you want to get, it is much easier to use Synaptic rather than apt-get. The results are the same.
On most of what has been said in this thread, I agree with slightlystoopid. Everyone else seems to be posting links to instructions to get codeblocks from the project maintaining codeblocks. It is simpler and probably better to get codeblocks using apt-get or Synaptic.
When you use apt-get or synaptic, any other software needed by the package you are installing will be installed automatically. That makes most of what you already did with apt-get to prepare for codeblocks unnecessary, but not in any way harmful.
Unlike most packages, codeblocks does not require for installation all of the other packages that you will need to really use codeblocks. Maybe you already covered what you need with the apt-get commands you already gave. But I suspect not. Once codeblocks is actually installed and you start trying to compile projects that you create in it, you will probably discover some other packages are missing, generic parts of the system needed for codeblocks to compile anything and/or packages specific to the type of project you decide to create in codeblocks.
I don't recall enough to predict exactly what extra items you might need. If you get stuck, post the error message from the attempt to do something in codeblocks and someone will tell you what extra package is needed to get past that error. It can be a little frustrating to start, but soon you will be past all those issues and codeblocks will operate smoothly.