KubuntuFeistyKde4Plan
Differences between revisions 3 and 4
|
Size: 2975
Comment:
|
Size: 2635
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: |
| Preparing kubuntu for kde4. | Preparing Kubuntu for KDE 4. |
| Line 12: | Line 13: |
| By packaging kde4 now we can work out packaging bugs and problems ahead of time. | By packaging KDE 4 now we can work out packaging bugs and problems ahead of time. |
| Line 14: | Line 16: |
| * Bobby the developer wants to make sure his kde4 application will work flawlessly when kde4 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 kde4 environment. She will want to be able to run her normal kde3 apps while in this environment. * Chuck the power user is curious and wants to run kde4 before it's officially supported. However most kde3 apps are not ported yet so he wants to run kde3 apps inside the kde4 environment. |
Bobby the developer wants to make sure his kde4 application will work flawlessly when kde4 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 kde4 environment. She will want to be able to run her normal kde3 apps while in this environment. Chuck the power user is curious and wants to run kde4 before it's officially supported. However most kde3 apps are not ported yet so he wants to run kde3 apps inside the kde4 environment. |
| Line 17: | Line 22: |
| 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. | Putting KDE4 in fiesty for developers and early adopters to ensure it works reliably and is ready to become the default as soon as KDE 4 is released. |
| Line 19: | Line 25: |
| Users need to be able to run kde3 apps inside a kde4 environment. 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. | Users need to be able to run KDE 3 apps inside a KDE 4 environment. We can not insist on only KDE 4 apps inside a KDE 4 environment because some users will want to run apps that have not been ported yet. |
| Line 21: | Line 27: |
| 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. |
== Implementation == |
| Line 24: | Line 29: |
| === Short term - while kde3 is still default === | === While KDE 3 is still default === |
| Line 28: | Line 33: |
| === Long term - when kde4 is the default === | === Post Feisty - when kde4 is the default === |
| Line 35: | Line 41: |
| == Implementation == === Code === === Data preservation and migration === == Unresolved issues == == BoF agenda and discussion == |
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 kde4 application will work flawlessly when kde4 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 kde4 environment. She will want to be able to run her normal kde3 apps while in this environment.
Chuck the power user is curious and wants to run kde4 before it's officially supported. However most kde3 apps are not ported yet so he wants to run kde3 apps inside the kde4 environment.
Scope
Putting KDE4 in fiesty for developers and early adopters to ensure 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 can not insist on only KDE 4 apps inside a KDE 4 environment because some users will want to run apps that have not been ported yet.
Implementation
While KDE 3 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.
- These packages will be in universe.
Post Feisty - 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. .
KubuntuFeistyKde4Plan (last edited 2008-08-06 16:26:48 by localhost)