KubuntuHardyKde4
|
Size: 2413
Comment:
|
Size: 2250
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 7: | Line 7: |
| * '''Packages affected''': | * '''Packages affected''': kde4* |
| Line 11: | 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 15: | 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 21: | 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 33: | Line 27: |
| Merge with Debian | Use the Debian packaging rather than our current packaging, but keep the namespaced source package names so kdebase remains as kde4base. |
| Line 35: | Line 29: |
| keep installed into /usr/lib/kde4 | 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 37: | Line 31: |
| 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/<binary>-kde4 | Binary packages need to be renamed to <package>-kde4 where they overlap in name with the KDE 3 version. |
| Line 39: | Line 33: |
| binary packages need to be renamed to <package>-kde4 if they overlap in name | 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. |
| Line 41: | Line 35: |
| Make sure kdebase-data and kdelibs5, kdebase-runtime-bin, kdebase-runtime-data, kde-icon-oxygen are coinstallable under both kde3 and kde4 in order to support the items athat are in main (kde-edu) | When packages are coinstallable, move KDE Edu and KDE Games into /usr/ and put them into main. |
| Line 43: | Line 37: |
| move these into /usr/ and put them into main w/ kde-edu along with kde-games | === Missing Tools === |
| Line 45: | Line 39: |
| ensure front-end tools get created for packagekit. This is not a requirement for hardy but should be started in its timeframe to ensure they are ready for hardy+1. | 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. |
| Line 47: | Line 41: |
| == CDs == | === CDs === |
| Line 49: | Line 43: |
| uni-distro as the script and include as much as can fit on the CD upload to Kubuntu.org for each release of kde4 build a CD built on Gutsy until Hardy releases then build on Hardy . |
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. |
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.
Launchpad Entry: kubuntu-hardy-kde4
Packages affected: kde4*
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 move kdeedu to main.,
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.
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.
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.
Migration
None at this stage, continue to use ~/.kde4 for data. Move to ~/,.kde for hardy+1
KubuntuHardyKde4 (last edited 2008-08-06 16:32:39 by localhost)