The Mer Wiki now uses your Mer user account and password (create account on https://bugs.merproject.org/)
Kickstart groups
(Mer's kickstart groups) |
|||
| Line 1: | Line 1: | ||
Mer uses package groups in [[:Category:kickstart|kickstart]] files when creating images to define what functionality to provide. | Mer uses package groups in [[:Category:kickstart|kickstart]] files when creating images to define what functionality to provide. | ||
| − | The definition of these groups is in | + | The definition of these groups is in http://gitweb.merproject.org/gitweb?p=mer/project-core.git;a=tree;f=patterns;hb=HEAD |
They are added into the repository by the createrelease.sh script. | They are added into the repository by the createrelease.sh script. | ||
Latest revision as of 14:29, 25 September 2012
Mer uses package groups in kickstart files when creating images to define what functionality to provide.
The definition of these groups is in http://gitweb.merproject.org/gitweb?p=mer/project-core.git;a=tree;f=patterns;hb=HEAD
They are added into the repository by the createrelease.sh script.
Contents |
[edit] mer-core
Mer core contains a minimal set of packages which will allow a Mer system to boot to a multi-user, console level system without basic networking.
[edit] mer-connectivity
The connectivity group adds networking, bluetooth, wireless and telephony.
[edit] mer-graphics-common
This group adds fonts and the uxlauncher. It does not provide an X or Wayland server.
[edit] mer-minimal-xorg
For devices that do not have a graphics HA a non-accelerated fb/vesa X server is provided with software rendering for GL.
[edit] mer-core-utils
It is often useful to do basic administration and tests on a device, these packages provide things like an editor, diff, tar, ssh as well as ofono and connman tests.
[edit] mer-debugging
The debugging group brings in gdb and some other debug symbols
