KubuntuHardyKde4

Differences between revisions 10 and 11
Revision 10 as of 2007-11-19 13:09:16
Size: 3073
Editor: wing-commander
Comment: review comments
Revision 11 as of 2007-11-22 17:43:17
Size: 3037
Editor: 87-194-29-91
Comment:
Deletions are marked like this. Additions are marked like this.
Line 16: Line 16:
 ''ScottJamesRemnant: still unconvinced about the separate CD idea; if you're convinced we can make an installable and usable CD, let's just do it by default.''
Line 24: Line 23:
Merge with Debian, keep packages co-installable and move kdeedu to main.
 ''ScottJamesRemnant: moving package to main prevents communit
y from being able to participate -- please leave it in universe.''
Merge with Debian, keep packages co-installable and use kdeedu by default in Edubuntu
Line 35: Line 33:
Make sure kdebase-data and kdelibs5, kdebase-runtime-bin, kdebase-runtime-data, kde-icon-oxygen are coinstallable with the KDE 3 packages in order to support packages in main.
 ''ScottJamesRemn
ant: packages should not be moved to main''
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 38: Line 35:
When packages are coinstallable, move KDE Edu and KDE Games into /usr/ and put them into main.
 ''ScottJamesRemnant: packages should not be moved to main''
Add kdeedu-kde4 to the Edubuntu edubuntu-addon-kde package, replacing kdeedu apps.
Line 41: Line 37:
''ScottJamesRemnant: Is there a meta package for all this? How do I get a KDE4 desktop in one click?'' 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.
Line 45: Line 41:
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.

''ScottJamesRemnant:
what packaging tool will be used for hardy?''
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.
Line 51: Line 45:
Use unidistro to create CDs with KDE 4 based on Gutsy and include as much as can fit on the CD. CDs should be made for each release of KDE 4. Upload to Kubuntu.org, emphasise that they are unsupported. 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.
Line 53: Line 47:
''ScottJamesRemnant: What is unidistro? How does that differ from our own CD creation process?'' 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 57: Line 51:
None at this stage, continue to use ~/.kde4 for data. Move to ~/,.kde for hardy+1

''Sco
ttJamesRemnant: How can so much work be put into such a short sentence?  Migration of KDE 3 to 4 settings is important.''
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.

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 [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.

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)