Dapper

Differences between revisions 2 and 3
⇤ ← Revision 2 as of 2006-04-13 19:50:57 →
Size: 1267
Editor: host-24-225-190-218
Comment: Created spec!
← Revision 3 as of 2006-04-19 15:00:56 → ⇥
Size: 1243
Editor: host-24-225-190-218
Comment:
Deletions are marked like this. Additions are marked like this.
Line 18: Line 18:
 * Detect whether breezy/dapper system (lsb-release -a) (./)
 * Detect the architecture (./)
 * Read the appropriate file (Status: Need to write file for Dapper, and merge the files for different archs into one)
 * Load gui based on the file (./)		 || Detect whether breezy/dapper system (lsb-release -c) || (./) ||
|| Detect the architecture || (./) ||
|| Read the packagelist file appropriate file || (./) ||
|| Load gui based on the file || (./) ||
Line 24: Line 24:
 * Work is being done in the branches/eudeb   * Initial Working Implementation is available in branches/eudeb

Summary

Spec for EasyUbuntu on Dapper, this page also lists possible improvements (packagewise) to EasyUbuntu for Dapper.

Rationale

People will inevitably want to use EasyUbuntu on Dapper. However, we want to retain backward compatibility with Breezy.

Design

  • An xml file containing the list of packages and configuration commands is present in the pkglist-release-arch.xml format, containing the different packages and configuration commands. EU will read and load a gui, and execute them based on the xml file

Implementation

Detect whether breezy/dapper system (lsb-release -c)

(./)

Detect the architecture

(./)

Read the packagelist file appropriate file

(./)

Load gui based on the file

(./)

Code

  • Initial Working Implementation is available in branches/eudeb

Outstanding issues

  • To handle translations from xml files, hopefully gui translations are automatic

CategorySpec

EasyUbuntu/Dapper (last edited 2008-08-06 16:28:05 by localhost)