Old Development Process

Caixa Mágica RPM based development process (PNG) - small Full size picture

Some important parts of development process:

  • 3 - ftp_sync: syncing between Cooker and CM RPMs. Changed CM RPMs should not be replaced by Cooker new RPMs but a warn should be issued (To-Do).
  • 4 - making the .sqfs with DrakX as well as all the installtion files necessary, including the kernel, isolinux and initrd. This requires the checkout of DrakX fron the SVN and the push of the installation files file into ISO image or FTP server.
  • 5 - gateway between SVN code repository and SVN RPMs. This is complex since a relation of "1 to 1+" .
  • 6 - the building factory is responsible for retrieving a package from SVN RPM repository where they are in the format SPEC + Tarball, rpmbuild'ing it and pushing into the FTP server or ISO image. This should be done in a chroot'ed environment. In the future, should exist a distributed system to process it over O2H cluster (kenobi?).
  • 7 - changes in cooker SVN code should be replicated in CM SVN. However, the merge is a manual process to avoid hard conflicts.

How to contribute:

  • A - Code contributions: senior developers can commit directly to the SVN, others should submit a patch using address "software AT caixamagica DOT pt"
  • B - Testing: test the tools and RPMs. Have fun!
  • C - Reporting: submit a bug report with problems found. After checking if the bug was not reported and, if not, reporting it.
Last modified 8 years ago Last modified on Feb 10, 2012, 3:31:50 PM

Attachments (4)

Download all attachments as: .zip