PackageSelection

Revision 8 as of 2005-04-23 09:24:13

Clear message

PackageSelection

Status

Introduction

Improve package selection mechanisms in Ubuntu to improve flexibility and maintainability.

This is NOT about choosing which packages to install, ship or support, but about the technical mechanisms used to implement these choices.

Rationale

Scope and Use Cases

  • Avoid hardcoding so many dependencies in debootstrap
  • Consider alternatives and improvements to the existing metapackage mechanism
    • Make it trivial to track additions and removals of packages from the standard package sets
    • Ensure smooth upgrades of systems based on the standard package sets
    • Allow users to express preferences about tracking changes

Implementation Plan

Data Preservation and Migration

Packages Affected

User Interface Requirements

Outstanding Issues

UDU BOF Agenda

  • Simplifying debootstrap maintenance
    • Install a minimal base system, install Ubuntu's "base" on top of it?
    • Resolve dependencies in debootstrap? (cdebootstrap?)
  • Tracking package selections
    • Review issues with the current metapackage approach
    • Consider solutions
      • Recommends
      • Tasks
      • Other alternatives
  • Is there a demand for "expansion packs" similar to Debian tasks?
    • Generic server
    • Development - what does it mean?
      • gcc, g++, libc-dev, make, dpkg-dev (build-essential)
      • Be able to build any source package included in the base system (build-essential + build-deps of base)
      • An approximate greatest common factor for building software from source tarballs (build-essential + some subset of -dev packages + autotools)
      • Be able to build any source package included in the selected install (build-essential + build-deps of base/desktop/server/etc.)
      • Some combination of the above
    • Web server
      • Apache
      • PHP
      • Selection of modules for each (db, auth, mod_{perl,python} ?)

UDU Pre-Work