The Mer Wiki now uses your Mer user account and password (create account on

OBS architecture naming

From Mer Wiki
Jump to: navigation, search

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"/>

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 latest_ or next_, depending if you build against latest or next Mer release repositories. After this comes the portname, see table below. Example of this in obs meta prj XML format is shown below:

 <repository name="latest_armv7hl">
   <path project="mer:devel" repository="latest_armv7hl"/>


 <repository name="latest_i486">
   <path project="mer:devel" repository="latest_i486"/>
Mer port name OBS scheduler name RPM architectures OBS project name in MDS OBS repository name in MDS Description
i486 i586 i486 Core:i486 Core_i486 Generic i486+ X86 port
i586 i586 i586, i686 Core:i586 Core_i586 SSSE3 enabled X86 port
x86_64 x86_64 x86_64 Core:x86_64 Core_x86_64 Generic 64 bit port
armv6l armv7el armv6l Core:armv6l Core_armv6l ARMv6 + VFP port
armv7l armv7el armv7l Core:armv7l Core_armv7l ARMv7 VFPv3-D16 port, softfp ABI
armv7hl armv8el armv7hl Core:armv7hl Core_armv7hl ARMv7 VFPv3-D16 port, hardfp ABI
armv7tnhl armv8el armv7hl, armv7nhl, armv7tnhl, armv7thl Core:armv7tnhl Core_armv7tnhl ARMv7 VFPv3-D16 port, hardfp ABI, NEON, Thumb2
mipsel mips mipsel Core:mipsel Core_mipsel MIPS32 O32 ABI port, hardfloat
Personal tools