OBS architecture naming

Revision as of 14:14, 18 January 2012

Repository naming convention

OBS has possibility to have multiple architectures compiled within one repository like shown below:

 <repository name="standard">
   <path project="Mer:Trunk:Base" repository="standard"/>
   <arch>i486</arch>
   <arch>i586</arch>
   <arch>armv6el</arch>
   <arch>armv7el</arch>
   <arch>armv8el</arch>
 </repository>

For Mer, however as we have only one architecture compiled in one repository, we can't use the repository structure shown above, but we need to have one repository per archtiecture. To prevent big mess with naming, it is recommended to follow the following naming convention with the repositories that are used to compile against Mer. The repository name consists of Mer_ after which comes the architecture, like Mer_{i486,i586,armv6el,armv7el,armv7hl}. Example of this in obs meta prj XML format is shown below:

 <repository name="Mer_i486">
   <path project="Mer:Trunk:Base" repository="Mer_i486"/>
   <arch>i486</arch>
 </repository>
 ...
 <repository name="Mer_armv7hl">
   <path project="Mer:Trunk:Base" repository="Mer_armv7hl"/>
   <arch>armv8el</arch>
 </repository>