Changes between Version 29 and Version 30 of WikiStart


Ignore:
Timestamp:
Feb 8, 2008, 10:47:57 PM (12 years ago)
Author:
Bruno Cornec
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WikiStart

    v29 v30  
    99I 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, ...
    1010
    11 Then I wanted to also work on another project called [http://trac.dploy.org dploy.org] which uses the great [http://www.LinuxCOE.org 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 :-)
     11Then I wanted to also work on another project called [http://trac.dploy.org dploy.org] which uses the great [http://www.LinuxCOE.org LinuxCOE]. However that LinuxCOE project had exactly the same issue as previously mentioned, no packaging, no install from CVS, so smaller community. And in order for me to put something on a production server, I want it packaged :-)
    1212
    13 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).
     13So 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). And thus was project-builder.org born !
    1414
    1515= Technical ideas around the project-builder.org (aka pb) project =
    1616
    1717 * use perl. It makes coding so much more efficient, powerful and also fun
    18  * 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 [http://trac.project-builder.org/browser/devel/pb-doc/AppConfig%3A%3AFile.patch 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: http://rt.cpan.org/Ticket/Display.html?id=28766
    19  * 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, ...)
     18 * make it independant from the CMS (flat, CVS, SVN, more to come), the VM (QEMU, more to come) or chroot (mock, pbuilder), the type of distro (RPM based, deb based, ebuild based, ...)
     19 * Reuse other Open Source Projects to help create a fully integrated build system, tacking in account building in parallel on various types of systems (virtual, physical, ...)
    2020
    2121= Examples of Project-Builder usage =