View on GitHub

Open Source Cluster Application Resources

Download this project as a .zip file Download this project as a tar.gz file

Documentations > Developer Documentations > OSCAR infrastructure > OSCAR Set Manager > Package Set Manager

Initial Implementation of Package Sets

OSCAR provides a basic notion of package sets, however the capability has never been fully implemented. This document presents the current status for an initial implementation of package sets, which will be enhanced/extended by the more complete implementation being pursued by Wesley Bland (Package Set Manager).

The current notion of a Default Package Set has been implemented, which is used to exclude OPKGs on a given Linux distribution.

Package Set Architecture

All package sets are defined in $(OSCAR_HOME)/share/package_sets/. In that directory a file describes a given package set for a specific Linux distribution and hardware architecture. They are organized as follow: ‘’$(OSCAR_HOME)/share/package_sets//--.xml

This allows us to maintain different files for each Linux distribution.

The schema of the XML file describing a package set is shown here:

<?xml version="1.0" encoding="ISO-8859-1"?>

Default Package Set

OSCAR currently supports only one package set: the “Default” package set. This package set defines the set of OPKG(s) that are available, by default, in OSCAR for a specific Linux distribution. For instance, the default package set for Debian Etch x86_64 is (filename: [source:trunk/share/package_sets/Default/debian-4-x86_64.xml debian-4-x86_64.xml]) :

<?xml version="1.0" encoding="ISO-8859-1"?>

The default package set is parsed by $(OSCAR_HOME)/scripts/package_config_xmls_to_database.