KubuntuHardyKde4
|
Size: 2482
Comment:
|
Size: 3073
Comment: review comments
|
| 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:foo * '''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. ''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 20: | Line 20: |
| 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 24: |
| You can have subsections that better describe specific parts of the issue. | 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 32: | Line 29: |
| 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 31: |
| === 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 33: |
| 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 35: |
| === Code Changes === | 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. ''ScottJamesRemnant: packages should not be moved to main'' |
| Line 40: | Line 38: |
| Code changes should include an overview of what needs to change, and in some cases even the specific details. | 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'' ''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?'' |
| Line 44: | Line 57: |
| 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 |
| Line 49: | Line 59: |
| == Test/Demo Plan == | ''ScottJamesRemnant: How can so much work be put into such a short sentence? Migration of KDE 3 to 4 settings is important.'' |
| Line 51: | Line 61: |
| 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.
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.
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.
ScottJamesRemnant: packages should not be moved to main
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
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.
KubuntuHardyKde4 (last edited 2008-08-06 16:32:39 by localhost)