ReducingDuplication

Revision 1 as of 2005-10-25 13:53:55

Clear message

Summary

We need to reduce library (and app) duplication in main as much as possible to make dapper's "supported for 5 years on the server" goal easier on all of us.

Rationale

Supporting multiple versions of similar codebases can be incredibly difficult and time-consuming. We should, rather, be concentrating on keeping ONE of everything (one libdb, one libmysqlclient, one libssl, one libpng, one set of mozilla libs, etc) in main, and punting the rest to universe (or oblivion)

Use cases

Scope

Design

Implementation

* Identify duplicate libs, make sure everything in main links to the "best" version, and kick the rest out. * Audit packages for local copies of libs (static libz, libdb, libpng, imlib, libpcre, and libneon have all been common in the past), and get us linking dynamically to packaged libraries everywhere possible.

Code

Data preservation and migration

Outstanding issues

BoF agenda and discussion