0install: Unterschied zwischen den Versionen

Aus Open Source Ecology - Germany
Zur Navigation springen Zur Suche springen
K
Zeile 2: Zeile 2:
 
0install is used as cross-platform dependency resolver for not having to package the projects' releases for multiple package managers.
 
0install is used as cross-platform dependency resolver for not having to package the projects' releases for multiple package managers.
 
This allows:
 
This allows:
 +
* modular, flexible development (single source principle).
 
* using the same toolchain for developing all kinds of projects (not only code)
 
* using the same toolchain for developing all kinds of projects (not only code)
 
* on all operating systems.
 
* on all operating systems.

Version vom 19. Dezember 2016, 22:49 Uhr

Why

0install is used as cross-platform dependency resolver for not having to package the projects' releases for multiple package managers. This allows:

  • modular, flexible development (single source principle).
  • using the same toolchain for developing all kinds of projects (not only code)
  • on all operating systems.
  • version control.
  • distributing, depending on modules in any revision and not only a certain release. (Releasing/tagging revisions is optional for development but still useful for indicating stable versions.)
  • automatic backup of projects.
  • easy testing of modules locally without breaking the system due to multiple versions of a package.
  • developer interaction (world wide team work) without releasing because Git is the base system and 0install just used for releases.
  • easily fetching, inspecting the sources of a project in a certain version. (e.g. to debug or further develop / fork a local version, this can be rebased later on)
  • preventing dependency mess.
  • linear project history (not mandatory but possible) and all other Git powers.

How

Install a module / package:

   0install add <repository.uri>/<module>.xml

Depend on a module by using the 0install XML file URI of the corresponding module repository.