A metapackage is a package that creates an installation tree in the Package Manager, or in other words, a package that supports the grouping and installation of multiple packages.
The Tizen Studio is based on metapackages to determine whether extensions are installed and to support integration between related tools, for example,
TV-2.4-samsung-public-Emulator. Metapackages are distinguished from regular packages by the
Figure: Metapackage dependency tree
There are 2 types of metapackages:
A metapackage cannot be dependent on both regular and meta packages.
Currently, there is no tool to verify a metapackage separately. Check the Git source to verify a metapackage.
Write the following additional information for extension meta packages:
These properties apply only when specified in the metapackage of the Extension Server.
Specifying the contents of an extension in Meta in the Main Repository is not handled as an extension.
C-ExtName(required): Extension name
C-Platform(required): Platform version name
C-Profile(required): Profile name
C-ExtProfile(required): Profile name of the subprofile (product) (specify the name of the profile)
C-ExtPath(required): Extension installation path
- Extension support if any type of distribution is available as a repository. - Deployed as a repository of all extensions (Repo Server, Image, Package)
For more information, see Configuring the Extension SDK Repository.