Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
en:docs:distribution [2013/04/20 13:26] – valerius | en:docs:distribution [2013/04/20 19:07] – valerius | ||
---|---|---|---|
Line 1: | Line 1: | ||
==== osFree distribution (draft I) ==== | ==== osFree distribution (draft I) ==== | ||
- | * osFree must use [[WarpIN]] as a package | + | osFree |
- | * support for [[repositories]]? | + | |
- | - This tool must be separate from WarpIN, i.e., it is specific to repositories, | + | * [[WarpIN]] as a package |
- | | + | * Also, a tool like eCoShop or Linux-like |
- | | + | * it must handle different package sources, like |
- | - | + | |
- | - WarpIN | + | * special directory layouts (on the current machine, or on remote http or ftp server), like diskette images with bundles (as used by IBM OS/2 distributions so, the installer will be capable to install old IBM OS/2 distributions as well) |
- | * response-file-driven | + | * other directory layouts, like APT or RPM repositories |
- | - response-file can be created manually | + | * different |
- | - response-file can be generated by UI (VIO or PM-based) | + | |
- | * so, installer must be divided into two separate parts: | + | * plain ZIP's with metainfo and installation scripts included (like it was in UnixOS/ |
- | - UI for choosing user options interactively, | + | * RPM - for software ported from UNIX. |
+ | * pack/ | ||
+ | * the package source frontend | ||
+ | | ||
+ | * The enhancements to WarpIN | ||
+ | * " | ||
+ | * Support for simultaneously existing versions of different packages with libraries, which are needed for different applications | ||
+ | * Maybe, " | ||
+ | * Coexistence of several package trees, which are updated separately, and do not influence other trees -- some analogies with source code repositories with branches | ||
+ | * Support for separating and merging | ||
+ | * response-file-driven | ||
+ | - response file can be created manually | ||
+ | - response file can be generated by UI (VIO or PM-based) | ||
+ | * so, installer must be divided into four separate parts: | ||
+ | - UI for choosing user options | ||
* textmode UI with pseudographics | * textmode UI with pseudographics | ||
* graphical, PM-based | * graphical, PM-based | ||
- | - installation engine, based on WarpIN with plugins. | + | - installation engine, based on invoking the package access frontend to retrieve the packages. It acts according the response file |
* it can be started by an experienced user, system administrator, | * it can be started by an experienced user, system administrator, | ||
+ | * installation engine is independent from UI and can be started separately; and more: the user can start the UI on one machine, save the resulting RSP (response) file and apply it on another machine, by pointing the installation engine to the needed RSP | ||
+ | * the single installer for initial machine setup, and subsequent option changes/ | ||
* also, DOS (DPMI)-based version of the installation engine and UI would be desired | * also, DOS (DPMI)-based version of the installation engine and UI would be desired | ||
* a Linux- or Win32-based version (?) | * a Linux- or Win32-based version (?) | ||
+ | - package access frontend, handling different package sources, via backends: | ||
+ | * different package storage/ | ||
+ | * different access protocols are implemented as special plugins | ||
+ | - enhanced WarpIN as the main package handling tool. | ||
+ | |||
+ | ~~DISCUSSION~~ | ||
+ |