Pharo in Open Build Service

Pharo uses Open Build service, OBS for short, to build its packages for different linux distributions. This page documents the decisions on the package versionning and naming. Specific implementation details are stored within the OBS repositories in companion readme files.

• Dev repository: https://build.opensuse.org/project/show/home:gpolito
• Stable repository: https://build.opensuse.org/project/show/devel:languages:pharo:stable

The repositories contain the following kind of packages

• Multiple pharo-vm-[major]-[minor] packages, one per major/minor vm version. Package managers allows us to install a specific version of a package, but not having two versions of the same package installed at the same time. Thus, we need a different package per important version. This package will be versionned using the VM version numbers.
  • See https://askubuntu.com/questions/758502/can-multiple-versions-of-the-same-package-co-exist-on-the-same-system
  • And https://bbs.archlinux.org/viewtopic.php?id=295791
• One pharo-[pharo version] package: a virtual package depending on the stable VM for that pharo version (somehow a reification of this table: https://github.com/pharo-project/pharo-vm/wiki/Versions,-Builds-and-Branches). This package will be versionned using the Pharo release version numbers.
• One pharo-[pharo version]-ide: package: a virtual package depending on pharo-[pharo version] and any IDE specific dependencies (think SDL). This package will be versionned using the Pharo release version numbers.