KubuntuFeistyKde4Plan
|
Size: 2275
Comment:
|
Size: 4881
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 6: | Line 6: |
| * '''Launchpad entry''': none yet * '''Packages affected''': |
* '''Launchpad entry''': https://features.launchpad.net/distros/ubuntu/+spec/kubuntu-feisty-kde4-plan * '''Packages affected''': kde4* |
| Line 10: | Line 10: |
| Users need to be able to run kde3 apps inside a kde4 environment. | Preparing Kubuntu for KDE 4. |
| Line 12: | Line 13: |
| We can't insist on only kde4 apps inside a kde4 environment because some users will want to run apps that have not been ported yet. | By packaging KDE 4 now, we can work out packaging bugs and problems ahead of time. |
| Line 14: | Line 16: |
| In the short term, a developer will want to run kde4 to develop/test and will need to run kde3 apps that haven't been ported. In the longer term, users will be running kde4 by default but will still occasionally need to run for example proprietary kde3 apps. |
Bobby the developer wants to make sure his KDE 4 application will work flawlessly when KDE 4 is officially released. She installs a current version of ubuntu/kubuntu and installs the kde4 packages. By following a simple guide, the developer sets up a KDE 4 environment. She will want to be able to run her normal KDE 3 apps while in this environment. Chuck the power user is curious and wants to run KDE 4 before it's officially supported. However, most KDE 3 apps are not ported yet, so he wants to run KDE 3 apps inside the KDE 4 environment. Sebas the KDE marketeer wants to have a KDE 4 CD available alongside the KDE 4.0 release. He uses the remastered Kubuntu CD for this purpose. |
| Line 17: | Line 24: |
| Putting kde4 in fiesty for developers and early adopters to insure it's easy to use. We need to consider the short term - when kde3 is default, and the long term - when kde4 is default. | Put KDE 4 in Feisty for developers and early adopters, to ensure that it works reliably and is ready to become the default as soon as KDE 4 is released. |
| Line 19: | Line 27: |
| === Short term - while kde3 is still default === * Use .kde4 instead of .kde for the settings. This should be automatically created when the kde4 environment is first run. Only app settings will be copied (i.e. no cache, no emails, etc). This will migrate bookmarks etc. * Prefix the kde4 packages with kde4. For example use the package name "kde4-koffice" for koffice 2. === Long term - when kde4 is the default === * kubuntu specific tools need to be ported. For example: windeco, splash, katapult, guidance, systemsettings, guidance, powersave. * .kde will be used. Any .kde4 will not be used or migrated. * Oxygen icons will be used for kde3 apps so symlinks etc will be needed so that kde3 apps use the kde4 icons. * We need to wait for upstream (kde developers) to fix running kde3 apps in kde4. David Faure has been making progress on this. * The kde4 packages will be rename to the original package names. For example "koffice" for koffice 2. This will replace the "kde4-koffice" package. . |
Users need to be able to run KDE 3 apps inside a KDE 4 environment. We cannot insist on KDE 4 apps only inside a KDE 4 environment because some users will want to run apps that have not been ported yet. |
| Line 30: | Line 29: |
| == Implementation == | == Feisty Implementation == |
| Line 32: | Line 31: |
| === Code === | While KDE 3 is still the default, we will package any upstream pre-releases of KDE 4 programmes as long as they compile and are mostly stable to run. We will use .kde4 instead of .kde for the settings directory to ensure the users's KDE 3 settings are not lost when using KDE 4. This should be automatically created when the KDE 4 environment is first run. Only application settings will be copied, soe.g. no cache or emails but it should migrate bookmarks. |
| Line 34: | Line 33: |
| === Data preservation and migration === | All packages will be prefixed with kde4-, so KOffice 2 will be kde4-koffice. The packages will install to /usr/lib/kde4 as currently in Edgy. These packages will be in universe. |
| Line 36: | Line 35: |
| == Unresolved issues == | Currently it is impossible to install KDE 3 and KDE 4 in the same place. We would like to install both to /usr when KDE 4 is released. To ensure this is possible we will work with upstream to ensure libexec support is implemented, which will put system binaries used by kdelibs (e.g. kded, kbuildsycoca, klaunch, kdeinit) in /usr/lib/kde4/libexec, not /usr/bin. This will prevent them from clashing with the same files from KDE 3. |
| Line 38: | Line 37: |
| == BoF agenda and discussion == | We will package the KDE 4 Oxygen icon theme for Kubuntu. We will implement the icon naming specification for KDE 4. This requires listing the desired icons in KDE 4, naming them in a manner consistent with the icon naming scheme. KDE 4 will be converted to the new names and the Tango icon tools should be extended to include the complete icon naming spec, creating symlinks to the old names which will allow the icons to be used in KDE 3 applications too, giving a consistent look and feel to a mixed KDE 3/4 desktop. Some applications developed within Kubuntu or heavily contributed to by Kubuntu developers will need to be ported to KDE 4. These are: * kwin-style-crystal window decoration. Query with upstream the progress on this * ksplah-moodin login splash. Query the maintainer, but since this is a fork of a Linspire project it may not get ported for a while, so likely we will need to port it ourselves, or drop it. * katapult. Maintainer (a Kubuntu developer) has some plans to port to KDE 4 but no timetable set. * guidance. Maintainers (Kubuntu developers) plan to port as soon as KDE 4 Python bindings are available * kde-systemsettings. Maintainer (Kubuntu developers) will port == After KDE 4 is Released == The KDE marketing team want a KDE 4 CD when KDE 4 is released (post feisty). We will help them make a remastered Kubuntu CD with KDE 4 (and KOffice 2). This will not be a supported version of Kubuntu nor on the Ubuntu archive servers, but will be for the earliest KDE 4 adopters to use, and allows us to evaluate if it is sane to move to using KDE 4 by default in the next Kubuntu release. Depending on the timing with the next Kubuntu release, we will start replacing KDE 3 packages with KDE 4 packages. The packages will be changed to install in /usr and have the kde4- prefix on the binary package name removed. .kde will be used for settings and any .kde4 directory will not be used or migrated. Oxygen icons will be used for KDE 3 and KDE 4 applications using the symlink method noted above. |
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: https://features.launchpad.net/distros/ubuntu/+spec/kubuntu-feisty-kde4-plan
Packages affected: kde4*
Summary
Preparing Kubuntu for KDE 4.
Rationale
By packaging KDE 4 now, we can work out packaging bugs and problems ahead of time.
Use cases
Bobby the developer wants to make sure his KDE 4 application will work flawlessly when KDE 4 is officially released. She installs a current version of ubuntu/kubuntu and installs the kde4 packages. By following a simple guide, the developer sets up a KDE 4 environment. She will want to be able to run her normal KDE 3 apps while in this environment.
Chuck the power user is curious and wants to run KDE 4 before it's officially supported. However, most KDE 3 apps are not ported yet, so he wants to run KDE 3 apps inside the KDE 4 environment.
Sebas the KDE marketeer wants to have a KDE 4 CD available alongside the KDE 4.0 release. He uses the remastered Kubuntu CD for this purpose.
Scope
Put KDE 4 in Feisty for developers and early adopters, to ensure that it works reliably and is ready to become the default as soon as KDE 4 is released.
Design
Users need to be able to run KDE 3 apps inside a KDE 4 environment. We cannot insist on KDE 4 apps only inside a KDE 4 environment because some users will want to run apps that have not been ported yet.
Feisty Implementation
While KDE 3 is still the default, we will package any upstream pre-releases of KDE 4 programmes as long as they compile and are mostly stable to run. We will use .kde4 instead of .kde for the settings directory to ensure the users's KDE 3 settings are not lost when using KDE 4. This should be automatically created when the KDE 4 environment is first run. Only application settings will be copied, soe.g. no cache or emails but it should migrate bookmarks.
All packages will be prefixed with kde4-, so KOffice 2 will be kde4-koffice. The packages will install to /usr/lib/kde4 as currently in Edgy. These packages will be in universe.
Currently it is impossible to install KDE 3 and KDE 4 in the same place. We would like to install both to /usr when KDE 4 is released. To ensure this is possible we will work with upstream to ensure libexec support is implemented, which will put system binaries used by kdelibs (e.g. kded, kbuildsycoca, klaunch, kdeinit) in /usr/lib/kde4/libexec, not /usr/bin. This will prevent them from clashing with the same files from KDE 3.
We will package the KDE 4 Oxygen icon theme for Kubuntu. We will implement the icon naming specification for KDE 4. This requires listing the desired icons in KDE 4, naming them in a manner consistent with the icon naming scheme. KDE 4 will be converted to the new names and the Tango icon tools should be extended to include the complete icon naming spec, creating symlinks to the old names which will allow the icons to be used in KDE 3 applications too, giving a consistent look and feel to a mixed KDE 3/4 desktop.
Some applications developed within Kubuntu or heavily contributed to by Kubuntu developers will need to be ported to KDE 4. These are:
- kwin-style-crystal window decoration. Query with upstream the progress on this
- ksplah-moodin login splash. Query the maintainer, but since this is a fork of a Linspire project it may not get ported for a while, so likely we will need to port it ourselves, or drop it.
- katapult. Maintainer (a Kubuntu developer) has some plans to port to KDE 4 but no timetable set.
- guidance. Maintainers (Kubuntu developers) plan to port as soon as KDE 4 Python bindings are available
- kde-systemsettings. Maintainer (Kubuntu developers) will port
After KDE 4 is Released
The KDE marketing team want a KDE 4 CD when KDE 4 is released (post feisty). We will help them make a remastered Kubuntu CD with KDE 4 (and KOffice 2). This will not be a supported version of Kubuntu nor on the Ubuntu archive servers, but will be for the earliest KDE 4 adopters to use, and allows us to evaluate if it is sane to move to using KDE 4 by default in the next Kubuntu release.
Depending on the timing with the next Kubuntu release, we will start replacing KDE 3 packages with KDE 4 packages. The packages will be changed to install in /usr and have the kde4- prefix on the binary package name removed. .kde will be used for settings and any .kde4 directory will not be used or migrated. Oxygen icons will be used for KDE 3 and KDE 4 applications using the symlink method noted above.
KubuntuFeistyKde4Plan (last edited 2008-08-06 16:26:48 by localhost)