en:docs:distribution

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
en:docs:distribution [2014/05/18 17:10] – valeriusen:docs:distribution [2016/02/04 01:04] (current) – [Package management] valerius
Line 1: Line 1:
-==== osFree distribution (draft I) ====+===== osFree distribution (draft I) =====
  
 osFree distribution principles: osFree distribution principles:
  
-=== Package management ===+==== Package management ====
  
-== WarpIN ==+=== WarpIN ===
  
   * [[http://home.clara.net/orac/os2.htm#warpin|WarpIN]] as a package management tool, with enhancements. WarpIN's purpose is maintaining the installed packages database, understanding the .WPI format, installing/deinstalling each package   * [[http://home.clara.net/orac/os2.htm#warpin|WarpIN]] as a package management tool, with enhancements. WarpIN's purpose is maintaining the installed packages database, understanding the .WPI format, installing/deinstalling each package
  
-== Package sources frontend ==+=== Package sources frontend ===
  
-  * Also, a tool like eCoShop or Linux-like repository access client is needed. It can be like apt or yum in Linux, but with OS/2 specifics. This tool must be separate from WarpIN, i.e., it is specific to repositories/package sources, not packages format. So: +  * Also, a tool like eCoMarket or Linux-like repository access client is needed. It can be like apt or yum in Linux, but with OS/2 specifics. This tool must be separate from WarpIN, i.e., it is specific to repositories/package sources, not packages format. So: 
     * it must handle different package sources, like      * it must handle different package sources, like 
       * files in the current directory        * files in the current directory 
       * 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)       * 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)
-      * other directory layouts, like APT or RPM repositories+      * other directory layouts, like APT or YUM repositories
     * different file transport protocols support, like ftp, http, etc, via plugins     * different file transport protocols support, like ftp, http, etc, via plugins
     * maybe, support for handling the different packages formats, other than WPI, because Netlabs, for example, prefer RPM's, so, it would be good to have support for them too, as they seem to be logical for ports from UNIX (but they are not suited well for native OS/2 applications). So, the support for the following formats would be desirable:      * maybe, support for handling the different packages formats, other than WPI, because Netlabs, for example, prefer RPM's, so, it would be good to have support for them too, as they seem to be logical for ports from UNIX (but they are not suited well for native OS/2 applications). So, the support for the following formats would be desirable: 
Line 22: Line 22:
       * pack/unpack-created bundles, as usual with IBM's OS/2 distributions       * pack/unpack-created bundles, as usual with IBM's OS/2 distributions
     *  the package source frontend will handle different package types via special plugins (or backends), and invoke different tools when installing packages (invoke WIC, UNZIP, UNPACK or RPM)     *  the package source frontend will handle different package types via special plugins (or backends), and invoke different tools when installing packages (invoke WIC, UNZIP, UNPACK or RPM)
-    * maybe, even, the possibility to create the decentralised network of package repositories is needed -- this will allow to use any nearest mirror, or use another mirror if the main mirror is down. Even we could try to create the repositories network on Peer-to-Peer basis ;)+    * maybe, even, the possibility to create the decentralised network of package repositories is needed -- this will allow to use any nearest mirror, or use another mirror if the main mirror is down. Even we could try to create the repositories network on Peer-to-Peer basis ;) (Use Bittorrent or any other protocol via a separate plugin,like the one for ftp/http)
  
-== WarpIN enhancements ==+=== WarpIN enhancements ===
  
   * The enhancements to WarpIN should include:   * The enhancements to WarpIN should include:
     * "Sticky" flag for packages which should not be upgraded     * "Sticky" flag for packages which should not be upgraded
-    * Support for simultaneously existing versions of different packages with libraries, which are needed for different applications+    * Support for simultaneously existing versions of different packages with libraries, which are needed for different applications (aka branches support)
     * Maybe, "Unstable" flag for apps and libraries, so, unstable package don't replace stable ones, they only create a separate branch in dependencies tree.     * Maybe, "Unstable" flag for apps and libraries, so, unstable package don't replace stable ones, they only create a separate branch in dependencies tree.
     * Coexistence of several package trees, which are updated separately, and do not influence other trees -- some analogies with source code repositories with branches     * 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 the branches, rollback of packages to an older (but stable) version      * Support for separating and merging the branches, rollback of packages to an older (but stable) version 
  
-=== The installer ===+==== The installer ====
  
   * response-file-driven installer:   * response-file-driven installer: