rPath Linux:rpl2 group structure
From rPath Wiki
(Redirected from rPathLinux:rpl2 group structure)
group-anaconda-deps
Tools included only for anaconda-templates and their build time dependencies
group-appliance-platform
The base group from which to build most common full-featured appliances. This is the group included from the group-appliance superclass. This group may change slightly from time to time to follow rPath's current recommended best practices. This will generally mean that additional packages may be added to provide additional functionality, such as hardware and software reporting and maintenance tools. This is a superset of group-core.
group-base
tools which automatically, simply by their presance on the system, add basic unix-y functionality to a system.
group-bootable
components necessary to boot a system in any anaconda-supported configuration and to login to said system and talk to a network. specifically, this group does *not* include components necessary to update the installed system using conary, raa, or any other in-band method
group-compat32
32 bit libraries for x86_64 systems
group-core
Individual components required to boot the system in any anaconda-supported install configuration, to log in to the system, to run Conary including a network connection, and dependencies of those troves. It is the normal core of a software appliance.
group-devel
All development tools All development-related components (:devel, :devellib, :perl, :python) from group-dist (automatically) This is a significant portion of the OS; the most important difference between a group-devel and everything install is that network services aren't automatically included in a group-devel install. (Additionally, other runtimes are not automatically included, such as the X server.)
group-dist
that which is shipped on the cd, dep complete
group-dist-base
This group contains packages that provide libraries and other files which resolve dependencies. This group is not selected by default at install time when installing from media. Components that are not required by other components being installed will be installed only in an "everything" install or if explicitly selected for installation. The only time that components are included without their packages are for the case of packages that are not entirely multilib-safe.
group-netserver
daemons that provide public services, and their direct dependencies
group-os
defination of the distro. anything included as part of rPath Linux must be part of group-os or one of its children
group-os-devel
All development-related components (:devel, :devellib, :perl, :python) from group-dist (automatically). In addition, packages which are build requirements but which we do not include on the media.
group-os-extras
Maintained packages that are not included on the media but are included in the distribution for some reason and do not best fit in some other subgroup of group-os, such as group-os-devel. This group may contain path conflicts.
group-printing
Tools required to implement a direct or indirect print service on the system. These may not be required to enable talking directly to a remote print queue from applications.
group-rails
Tools that are required to support Ruby on Rails.
group-rpl-livecd
livecd group. the defination of what goes on the livecd
group-text-devel
Simple development environment used for building live images that support development from a text-mode login environment
group-text-tools
General-purpose text tools, including general programs that are useful without running X. Must not pull in X via dependencies.
group-X
Tools that are generally useful only for a graphical desktop but are not specific to GNOME, KDE, or some other desktop environment. This includes all the component of the x.org components that we build, but does not include applications that belong in group-X-applications.
group-X-applications
Applications that are generally useful only if you have a graphical desktop but are not specific to GNOME, KDE, or some other desktop environment.
