The Mer Wiki now uses your Mer user account and password (create account on https://bugs.merproject.org/)

OBS architecture naming

From Mer Wiki
(Difference between revisions)
Jump to: navigation, search
m (OBS moved to OBS architecture naming: OBS is too generic)
(→‎Repository naming convention)
Line 15: Line 15:
 
   <repository name="Mer_i486">
 
   <repository name="Mer_i486">
 
     <path project="Mer:Trunk:Base" repository="Mer_i486"/>
 
     <path project="Mer:Trunk:Base" repository="Mer_i486"/>
−
     <arch>i486</arch>
+
     <arch>i586</arch>
 
   </repository>
 
   </repository>
 
   ...
 
   ...
Line 22: Line 22:
 
     <arch>armv8el</arch>
 
     <arch>armv8el</arch>
 
   </repository>
 
   </repository>
 +
 +
{|
 +
|Mer port name
 +
|OBS scheduler name
 +
|RPM architecture bottom and top
 +
|OBS project name in fakeobs
 +
|OBS repository name in fakeobs
 +
|Description
 +
|-
 +
|i486
 +
|i586
 +
|i486
 +
|Core:i486
 +
|Core_i486
 +
|Generic i486+ X86 port
 +
|-
 +
|i586
 +
|i586
 +
|i586, i686
 +
|Core:i586
 +
|Core_i586
 +
|SSSE3 enabled X86 port
 +
|-
 +
|armv6l
 +
|armv6l, armv6l
 +
|armv7el
 +
|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
 +
|-
 +
|mipsel
 +
|mips
 +
|mipsel
 +
|Core:mipsel
 +
|Core_mipsel
 +
|MIPS32 O32 ABI port, hardfloat
 +
|}
  
 
[[Category:obs]]
 
[[Category:obs]]

Revision as of 15:12, 13 February 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>i586</arch>
 </repository>
 ...
 <repository name="Mer_armv7hl">
   <path project="Mer:Trunk:Base" repository="Mer_armv7hl"/>
   <arch>armv8el</arch>
 </repository>
Mer port name OBS scheduler name RPM architecture bottom and top OBS project name in fakeobs OBS repository name in fakeobs Description
i486 i586 i486 Core:i486 Core_i486 Generic i486+ X86 port
i586 i586 i586, i686 Core:i586 Core_i586 SSSE3 enabled X86 port
armv6l armv6l, armv6l armv7el 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
mipsel mips mipsel Core:mipsel Core_mipsel MIPS32 O32 ABI port, hardfloat
Retrieved from "https://wiki.merproject.org/wiki/index.php?title=OBS_architecture_naming&oldid=967"
Personal tools