Version 92 (modified by vsilva, 3 years ago) (diff)


Welcome to the home of Caixa Mágica Linux development


If you're looking for the main Caixa Mágica website you can find it here.

The Caixa Mágica Linux development consists mainly in:

Since 2000 and until CM 11, Caixa Mágica had developed the installer / configurator (lucas/licas/xLucas/xLicas) from scratch and shared the base with SuSE.

The Caixa Mágica versions 12, 14 and 15 shared the Mandriva framework (Installer and Configurator and core RPMs). It was not entirely the same code since we were committed to core technologies that were not in Mandriva roadmap like Apt,.... Read the LetterToTheCommunity about the moving to Mandriva (portuguese).

From Caixa Mágica 16 onwards we decided to move to a Debian core distribution, using mainly Ubuntu as the package base. You can read the announcement here

Although there are several payed developers in the development process, Caixa Mágica has always been open to contributions.

How to contribute

Bug reporting

  • Anytime something in your Caixa Mágica usage either doesn't work as expected or doesn't work at all please fill up a bug report here;
  • Make sure that you check first if the bug was not reported yet and, if not, report it.

Testing development versions

  • When a new version of Caixa Mágica is being developed, testing versions (usually called Alpha or Beta versions) are release for public testing. You can help by testing those versions and filling bug reports here;

Code contributions

  • Senior developers can commit directly to the SVN, others should submit a patch using address "software AT caixamagica DOT pt". See here how you can download a package source code and create a patch for us to test.
  • Everyone can send DEB sources to the contributions repository. Just use our Contribware website to do so in a very easy way.

Development process

Caixa Mágica DEB based development process - Medium size
Full size picture


There are three mais sources for the Caixa Mágica Linux Distribution:


The build system has two main steps:

  • Check the sources for updates, and either places the updates on the testing repository directly, or sends the sources to our SVN (subversion) repository;
  • Packages updated in our SVN (subversion) repository, or sent as contributions via Contribware are automaticaly built on our BuildFarm.


Packages either directly from upstream, or built in our BuildFarm are added to the testing repositories, and after testing are moved to the final, publicly available repository

Summer Internships



Attachments (2)

Download all attachments as: .zip