KubuntuHardyKde4

Differences between revisions 9 and 10
Revision 9 as of 2007-11-02 19:49:54
Size: 2250
Editor: 12
Comment:
Revision 10 as of 2007-11-19 13:09:16
Size: 3073
Editor: wing-commander
Comment: review comments
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 23: Line 24:
Merge with Debian, keep packages co-installable and move kdeedu to main., Merge with Debian, keep packages co-installable and move kdeedu to main.
 ''ScottJamesRemnant: moving package to main prevents community from being able to participate -- please leave it in universe.''
Line 34: Line 36:
 ''ScottJamesRemnant: packages should not be moved to main''
Line 36: Line 39:
 ''ScottJamesRemnant: packages should not be moved to main''

''ScottJamesRemnant: Is there a meta package for all this? How do I get a KDE4 desktop in one click?''
Line 41: Line 47:
''ScottJamesRemnant: what packaging tool will be used for hardy?''
Line 44: Line 52:

''ScottJamesRemnant: What is unidistro? How does that differ from our own CD creation process?''
Line 49: Line 59:
''ScottJamesRemnant: How can so much work be put into such a short sentence? Migration of KDE 3 to 4 settings is important.''

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.

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

Rationale

KDE 4 rocks, we should support it.

Design

Merge with Debian, keep packages co-installable and move kdeedu to main.

  • ScottJamesRemnant: moving package to main prevents community from being able to participate -- please leave it in universe.

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 coinstallable with the KDE 3 packages in order to support packages in main.

When packages are coinstallable, move KDE Edu and KDE Games into /usr/ and put them into main.

ScottJamesRemnant: Is there a meta package for all this? How do I get a KDE4 desktop in one click?

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.

ScottJamesRemnant: what packaging tool will be used for hardy?

CDs

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.

ScottJamesRemnant: What is unidistro? How does that differ from our own CD creation process?

Migration

None at this stage, continue to use ~/.kde4 for data. Move to ~/,.kde for hardy+1

ScottJamesRemnant: How can so much work be put into such a short sentence? Migration of KDE 3 to 4 settings is important.


CategorySpec

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