Changes

Jump to navigation Jump to search
Line 83: Line 83:     
The same component could be a part of different bundles. In that case, the different package implementations will contain the same bundle component tarball.
 
The same component could be a part of different bundles. In that case, the different package implementations will contain the same bundle component tarball.
 +
 +
== OBS ==
 +
 +
=== [Package] ===
 +
 +
If this section is present, the recipe should be used only for defining native packages on http://refinery.sugarlabs.org.
 +
 +
'''package''' = <native-package-name>
 +
 +
Name of a package (binary package, for binary-based distributions) associated with the recipe. Option value might be a name of virtual package (a name that original package provides).
 +
 +
'''devel''' = <native-package-name>
 +
 +
Name of devel package (for binary-based distributions) associated with the recipe. Option value might be a name of virtual package (a name that original package provides).
 +
 +
'''type''' = <package-type>
 +
 +
Packaging system type that describing package belongs to. Should be used only for non-rpm/deb packages. Supported values (case-sensitive):
 +
 +
* ''Gentoo'' for Gentoo distribution,
 +
* ''Slack'' for Slackware distribution,
 +
* ''Ports'' for FreeBSD Ports.
 +
 +
'''repo''' = <glob-mask> [; ...]
 +
 +
Case insensitive glob masks of repository names in OBS project that current recipe belongs to. If option is absent, aliasing will be applied to all repositories.
 +
 +
Aliasing might be different for different repositories, e.g., if repositories come from several GNU/Linux distributions. In that case per-repository Package sections (with setting ''repo'' option) should be used:
 +
 +
[Package/<arbitrary-unique-name>]
    
== Pitfalls ==
 
== Pitfalls ==

Navigation menu