29d6678fd5
Having one monolithic packages directory makes it hard to find things and is generally overwhelming. This commit splits it into several logical sections roughly based on function, recipes.txt gives more information about the classifications used. The opportunity is also used to switch from "packages" to "recipes" as used in OpenEmbedded as the term "packages" can be confusing to people and has many different meanings. Not all recipes have been classified yet, this is just a first pass at separating things out. Some packages are moved to meta-extras as they're no longer actively used or maintained. Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
14 lines
1.1 KiB
Text
14 lines
1.1 KiB
Text
recipes-bsp - Anything with links to specific hardware or hardware configuration information
|
|
recipes-connectivity - Libraries and applications related to communication with other devices
|
|
recipes-core - What's needed to build a basic working Linux image including commonly used dependencies
|
|
recipes-devtools - Tools primarily used by the build system (but can also be used on targets)
|
|
recipes-extended - Applications which whilst not essential add features compared to the alternatives in
|
|
core. May be needed for full tool functionality or LSB compliance.
|
|
recipes-gnome - All things related to the GTK+ application framework
|
|
recipes-graphics - X and other graphically related system libraries
|
|
recipes-kernel - The kernel and generic applications/libraries with strong kernel dependencies
|
|
recipes-multimedia - Codecs and support utilties for audio, images and video
|
|
recipes-qt - All things related to the QT application framework
|
|
recipes-sato - The Sato demo/reference UI/UX, its associated apps and configuration
|
|
|