Version 28 (modified by Bruno Cornec, 13 years ago) (diff)


Welcome to Project-Builder Wiki

Design Ideas around the project

Since 2005 that I took over the maintenance of the MondoRescue project, I have passed time developing code on the periphery of the project to allow me to easily build packages from Subversion, deliver them, manage them, ...

I met a lot of Open Source project which are suffering from the same barrier for their adoption as mondo suffered in the past: without native packaging for your distribution you have much less people testing your software, trying it, less chance to be integrated in distributions, ...

Then I wanted to also work on another project called which uses the great LinuxCOE. However that LinuxCOE project had exactly the same issue as previously mentioned, no packaging, on install from CVS, so smaller community. And in order for me to put something on a prouction server, I want it packaged :-)

So I decided it could be a good idea to reuse the scripts made for mondo to package LinuxCOE. However, they were too specific, even if the ideas could be reused (that was my 3rd generation of build scripts, so ideas were more advanced than the code).

Technical ideas around the (aka pb) project

  • use perl. It makes coding so much more efficient, powerful and also fun
  • use AppConfig?. A lot of information is managed under a configuration file format and AppConfig? makes it trivial to handle them. BTW look at that patch as the versions of AppConfig? from 1.63 and up to 1.66 at least have a bug for handling hashes correctly this fixes. Cf:
  • make it independant from the CMS (flat, CVS, SVN, more to come), the VM (QEMU, more to come), the type of distro (RPM based, deb based, ebuild based, ...)

Examples of Project-Builder usage

Concerning trac

For a complete list of local wiki pages, see TitleIndex.

Trac is brought to you by Edgewall Software, providing professional Linux and software development services to clients worldwide. Visit for more information.