Editing Task:Maemo Community distribution
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 7: | Line 7: | ||
Provide a community distribution less encumbered by Nokia's corporate policies that is more flexible in its packaging, bundles community software, and modifies Nokia software and packaging with community patches. | Provide a community distribution less encumbered by Nokia's corporate policies that is more flexible in its packaging, bundles community software, and modifies Nokia software and packaging with community patches. | ||
| - | == Sort out a repository == | + | == Tasks == |
| + | |||
| + | To get to a workable distribution, we first need to consider a number of problems. | ||
| + | |||
| + | === Sort out a repository === | ||
It would be preferable to simply distribute all packages in Extras, but this adds complexity and may simply be impossible to do cleanly, as these packages are likely to interfere with SSU and confuse users. Extras-devel is probably more appropriate, but that would force users wanting to use the community distribution to be exposed to unstable software. Not ideal. The simpler and cleaner option is to use a separate repository either on repository.maemo.org or a 3rd party repository somewhere else. | It would be preferable to simply distribute all packages in Extras, but this adds complexity and may simply be impossible to do cleanly, as these packages are likely to interfere with SSU and confuse users. Extras-devel is probably more appropriate, but that would force users wanting to use the community distribution to be exposed to unstable software. Not ideal. The simpler and cleaner option is to use a separate repository either on repository.maemo.org or a 3rd party repository somewhere else. | ||
| Line 25: | Line 29: | ||
After [https://bugs.maemo.org/show_bug.cgi?id=3602 some discussion], it seems like option 3 is likely the most workable. Some scripting could be implemented to help reduce manual overhead, but this is likely a goal for later. | After [https://bugs.maemo.org/show_bug.cgi?id=3602 some discussion], it seems like option 3 is likely the most workable. Some scripting could be implemented to help reduce manual overhead, but this is likely a goal for later. | ||
| - | == osso-software-version-community == | + | === osso-software-version-community === |
We need to provide a community version of osso-software-version that has a modified dependencies list that provides the community distribution. A couple considerations should be kept in mind, dependencies on proprietary junk will be removed (skype, gizmo, etc.), dependencies will be setup to allow easy installation of updated system libraries and 3rd-party patches (rotation, 48MHz, etc.), and unnecessary packages that shouldn't be part of the OS-proper will be moved to separate packages that can be uninstalled through application manager (bundled PDFs, images, movies, etc.). | We need to provide a community version of osso-software-version that has a modified dependencies list that provides the community distribution. A couple considerations should be kept in mind, dependencies on proprietary junk will be removed (skype, gizmo, etc.), dependencies will be setup to allow easy installation of updated system libraries and 3rd-party patches (rotation, 48MHz, etc.), and unnecessary packages that shouldn't be part of the OS-proper will be moved to separate packages that can be uninstalled through application manager (bundled PDFs, images, movies, etc.). | ||
| - | === Add === | + | ==== Add ==== |
Community enhancements that should be added to the default community distribution. | Community enhancements that should be added to the default community distribution. | ||
| Line 37: | Line 41: | ||
* '''e2fsprogs''': For handling ext2/3 filesystems. | * '''e2fsprogs''': For handling ext2/3 filesystems. | ||
| - | === Remove === | + | ==== Remove ==== |
Useless and proprietary stuff to be removed. | Useless and proprietary stuff to be removed. | ||
| Line 45: | Line 49: | ||
* '''skype-installer''': Remove proprietary advertising. | * '''skype-installer''': Remove proprietary advertising. | ||
| - | === Modify === | + | ==== Modify ==== |
Existing packages that should be enhanced. | Existing packages that should be enhanced. | ||
| Line 57: | Line 61: | ||
* '''preinstalled-videos''': Move to its own package. | * '''preinstalled-videos''': Move to its own package. | ||
| - | == Patches, hacks, and modifications == | + | === Patches, hacks, and modifications === |
As a community distribution, we're not burdened by corporate policy and decision making, so we're free to include interesting and useful patches and hacks that Nokia cannot. | As a community distribution, we're not burdened by corporate policy and decision making, so we're free to include interesting and useful patches and hacks that Nokia cannot. | ||
| - | === Application | + | ==== Application Manager ==== |
A community distribution could serve as an easier way to include community branches of Nokia open source applications. The Application manager is a particularly good candidate for this, and could include patches to: | A community distribution could serve as an easier way to include community branches of Nokia open source applications. The Application manager is a particularly good candidate for this, and could include patches to: | ||
| Line 70: | Line 74: | ||
* Improve the category view. | * Improve the category view. | ||
| - | === bootmenu === | + | ==== bootmenu ==== |
Including a modified initfs both increases versatility (by allowing easier multiboot), and gives all users access to recovery modes for when things go wrong. A graphical bootmenu should be put together to increase user-friendliness. | Including a modified initfs both increases versatility (by allowing easier multiboot), and gives all users access to recovery modes for when things go wrong. A graphical bootmenu should be put together to increase user-friendliness. | ||
| - | ==== Configuration ==== | + | ===== Configuration ===== |
By default, a bundled initfs should boot immediately to the default partition, offering a short window to enter recovery mode, but no partition selection. Users can then add partitions either through a .item system on the console with a "flasher" script that commits the appropriate filesystem changes, or through an easy-to-use control panel. | By default, a bundled initfs should boot immediately to the default partition, offering a short window to enter recovery mode, but no partition selection. Users can then add partitions either through a .item system on the console with a "flasher" script that commits the appropriate filesystem changes, or through an easy-to-use control panel. | ||
| - | ==== Recovery mode ==== | + | ===== Recovery mode ===== |
The bootmenu should offer a number of recovery modes in addition to the existing USBNet recovery. The recovery mode should offer the option to make backup images (to put on one of the cards or other mass storage device), restore backup images, and maybe offer some sort of framebuffer console for use with a hardware keyboard. | The bootmenu should offer a number of recovery modes in addition to the existing USBNet recovery. The recovery mode should offer the option to make backup images (to put on one of the cards or other mass storage device), restore backup images, and maybe offer some sort of framebuffer console for use with a hardware keyboard. | ||
Learn more about Contributing to the wiki.