KubuntuHardyKde4

Differences between revisions 2 and 13 (spanning 11 versions)
Revision 2 as of 2007-10-19 11:06:13
Size: 2497
Editor: 87-194-29-91
Comment:
Revision 13 as of 2008-08-06 16:32:39
Size: 3038
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was renamed from KubuntuHardyKde4
Line 5: Line 6:
 * '''Launchpad Entry''': UbuntuSpec:kubuntu-gutsy-kde4
 * '''Packages affected''':
 * '''Launchpad Entry''': UbuntuSpec:kubuntu-hardy-kde4
 * '''Packages affected''': kde4*
Line 10: Line 11:
This should provide an overview of the issue/functionality/change proposed here. Focus here on what will actually be DONE, summarising that so that other people don't have to read the whole spec. Packaging KDE 4 in Hardy.
Line 14: Line 15:
This section should include a paragraph describing the end-user impact of this change. It is meant to be included in the release notes of the first release in which it is implemented. (Not all of these will actually be included in the release notes, at the release manager's discretion; but writing them is a useful exercise.)

It is mandatory.
KDE 4 packages are available with selected modules supported as default. CDs are available for those who prefer a complete KDE 4 environment without LTS.
Line 20: Line 19:
This should cover the _why_: why is this change being proposed, what justifies it, where we see this justified.

== Use Cases ==

== Assumptions ==
KDE 4 rocks, we should support it.
Line 28: Line 23:
You can have subsections that better describe specific parts of the issue. Merge with Debian, keep packages co-installable and use kdeedu by default in Edubuntu
Line 32: Line 27:
This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like: Use the Debian packaging rather than our current packaging, but keep the namespaced source package names so kdebase remains as kde4base.
Line 34: Line 29:
=== UI Changes === Keep packages installed into /usr/lib/kde4. Have the packaging create wrapper scripts for each binary in /usr/bin/<binary>-kde4 which export required PATHs and run /usr/lib/kde4/<binary>. Also create menu entries in /usr/share/applications/<binary>-kde4 which point to /usr/lib/kde4/bin/<binary>-kde4.
Line 36: Line 31:
Should cover changes required to the UI, or specific UI that is required to implement this Binary packages need to be renamed to <package>-kde4 where they overlap in name with the KDE 3 version.
Line 38: Line 33:
=== Code Changes === Make sure kdebase-data and kdelibs5, kdebase-runtime-bin, kdebase-runtime-data, kde-icon-oxygen are co-installable with the KDE 3 packages in order to allow KDE 3 and 4 to be run side by side.
Line 40: Line 35:
Code changes should include an overview of what needs to change, and in some cases even the specific details. Add kdeedu-kde4 to the Edubuntu edubuntu-addon-kde package, replacing kdeedu apps.

Create a seed called kubuntu-kde4 with associated meta package kubuntu-kde4-desktop to be an easy way to install a KDE 4 desktop. Add a .desktop file to app-install-data so it can be easily installed from adept-installer or gnome-app-install.

=== Missing Tools ===

The major missing application in KDE 4 compared to KDE 3 is packaging tools. Work with upstream to create front-end KDE tools for PackageKit and the backend for apt. This is not a requirement for hardy but should be started in its timeframe to ensure they are ready for hardy+1. For Hardy we will use the existing Adept tools.

=== CDs ===

Create daily kubuntu-kde4 Hardy CDs from the kubuntu-kde4 CD. These would not be put on releases.ubuntu.com at release time but kept on cdimage.ubuntu.com and marketed as an alternative CD for the experimental.

For the 4.0 release, Hardy will not be stable enough for CDs. Use [[https://launchpad.net/unidistro|unidistro]] to create CDs with KDE 4 based on Gutsy and include as much as can fit on the CD. Unidistro is easier to create quick custom CDs with than our own CD creation process. CDs should be made for each release of KDE 4. Upload to Kubuntu.org, emphasise that they are unsupported.
Line 44: Line 51:
Include:
 * data migration, if any
 * redirects from old URLs to new ones, if any
 * how users will be pointed to the new way of doing things, if necessary.
None at this stage, continue to use ~/.kde4 for data. Move to ~/.kde for hardy+1 after extensive testing that settings are safely migrated from KDE 3 to 4.
Line 49: Line 53:
== Test/Demo Plan ==

It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during CD testing, and to show off after release.

This need not be added or completed until the specification is nearing beta.

== Outstanding Issues ==

This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.

== BoF agenda and discussion ==

Handle the 4.0 release, merge with Debian and get it in sync with Ubuntu features.

Please check the status of this specification in Launchpad before editing it. If it is Approved, contact the Assignee or another knowledgeable person before making changes.

Summary

Packaging KDE 4 in Hardy.

Release Note

KDE 4 packages are available with selected modules supported as default. CDs are available for those who prefer a complete KDE 4 environment without LTS.

Rationale

KDE 4 rocks, we should support it.

Design

Merge with Debian, keep packages co-installable and use kdeedu by default in Edubuntu

Implementation

Use the Debian packaging rather than our current packaging, but keep the namespaced source package names so kdebase remains as kde4base.

Keep packages installed into /usr/lib/kde4. Have the packaging create wrapper scripts for each binary in /usr/bin/<binary>-kde4 which export required PATHs and run /usr/lib/kde4/<binary>. Also create menu entries in /usr/share/applications/<binary>-kde4 which point to /usr/lib/kde4/bin/<binary>-kde4.

Binary packages need to be renamed to <package>-kde4 where they overlap in name with the KDE 3 version.

Make sure kdebase-data and kdelibs5, kdebase-runtime-bin, kdebase-runtime-data, kde-icon-oxygen are co-installable with the KDE 3 packages in order to allow KDE 3 and 4 to be run side by side.

Add kdeedu-kde4 to the Edubuntu edubuntu-addon-kde package, replacing kdeedu apps.

Create a seed called kubuntu-kde4 with associated meta package kubuntu-kde4-desktop to be an easy way to install a KDE 4 desktop. Add a .desktop file to app-install-data so it can be easily installed from adept-installer or gnome-app-install.

Missing Tools

The major missing application in KDE 4 compared to KDE 3 is packaging tools. Work with upstream to create front-end KDE tools for PackageKit and the backend for apt. This is not a requirement for hardy but should be started in its timeframe to ensure they are ready for hardy+1. For Hardy we will use the existing Adept tools.

CDs

Create daily kubuntu-kde4 Hardy CDs from the kubuntu-kde4 CD. These would not be put on releases.ubuntu.com at release time but kept on cdimage.ubuntu.com and marketed as an alternative CD for the experimental.

For the 4.0 release, Hardy will not be stable enough for CDs. Use unidistro to create CDs with KDE 4 based on Gutsy and include as much as can fit on the CD. Unidistro is easier to create quick custom CDs with than our own CD creation process. CDs should be made for each release of KDE 4. Upload to Kubuntu.org, emphasise that they are unsupported.

Migration

None at this stage, continue to use ~/.kde4 for data. Move to ~/.kde for hardy+1 after extensive testing that settings are safely migrated from KDE 3 to 4.


CategorySpec

KubuntuHardyKde4 (last edited 2008-08-06 16:32:39 by localhost)