Revision as of 20:19, 7 February 2012

Mer source is in kept in git and there is a gitweb view here: http://gitweb.merproject.org/gitweb.

There are a number of project areas.

mer-core

The source for the actual packages in a Mer base system live here.

Packages somewhat related to cross compile (ie, don't exist in the x86 port) go in here

When Mer moves to Scratchbox2, the approach to cross-compilation that requires these packages will be deprecated.

This area contains:

The code used by the Mer project automation systems. This includes the code for the QA checks run when changes are submitted to Core.

This area essentially describes the core. It contains configuration for the OBS and other build tools used to build Mer. This includes:

OBS prjconfig
A snapshot of the packages in the core.
Repository pattern / group definitions used in kickstarts (see Kickstart groups) are in /patterns/
scripts used when releasing or exchanging Mer

Contributions to any part of Mer source is welcome.

Mer does not currently track upstream sources but there is a bug about that: https://bugs.merproject.org/show_bug.cgi?id=97

Mer uses gerrit to manage the git repositories.

@@ Line 9: / Line 9: @@
 == mer-crosshelpers ==
-Before using [[Scratchbox2]], Mer used an approach to cross-compilation that required these packages.
+Packages somewhat related to cross compile (ie, don't exist in the x86 port) go in here
+When Mer moves to [[Scratchbox2]], the approach to cross-compilation that requires these packages will be deprecated.
 == mer ==
@@ Line 38: / Line 40: @@
 Mer does not currently track upstream sources but there is a bug about that: https://bugs.merproject.org/show_bug.cgi?id=97
+= Management =
+Mer uses gerrit to manage the git repositories.