RPM&YUM for OS/2

Version: 
4.13.0 & 3.4.3
Release date: 
Friday, 9 June, 2017

License:

Interface:

Authors/Port authors:

Package Manager (RPM) is a powerful command line driven package management system capable of installing, uninstalling, verifying, querying, and updating computer software packages. YUM is an automatic updater and package installer/remover for rpm systems.

The Arca Noae Package Manager makes easy dealing with RPM/YUM packages.

This software is distributed in two modes:
  • as compressed package that you have to download and manually install; if prerequisites are required, you will have to manually install them too;
  • as RPM package; you can install it using your favorite rpm package manager, that will take care to download and install both the software and its prerequisites.
Choose the installation mode that you prefer. Please note that not all the versions are available in both the installation modes.

Installation with rpm

This program is installable using the rpm package manager. See below for the install string. Required prerequisites are automatically processed by the package manager and, if needed, downloaded and installed.

rpm-4.13.0-18.oc00 (29/03/2019)
Repository: Netlabs stable
yum-3.4.3-10.oc00 (09/06/2016)
Repository: Netlabs stable

Manual installation

Self-installing WarpIN package. See below for download link(s) and detailed installation instructions. RPM-YUM "i386" package is for generic i386 architecture, while "p4" package is for modern PCs based on Pentium 4 processor or better.

Once the installation is completed, you can remove the WarpIN package.

GENERAL CONSIDERATIONS ABOUT RPM-YUM:

Selecting a target drive for installation, consider the following:

  • The target drive should be big enough to install all software you need from RPM repositories. A good estimate is 5G of free space (this counts future RPM releases of big applications like Java, OpenOffice and so on). If you are a developer, you should double this reserve (so that it can fit the compiler and various frameworks).
  • The installer will create a simplified Unix tree on the target drive. This single tree will be used by all software ported from Unix/Linux and distributed with RPM.
  • It is a good idea to select the boot volume as a target drive for the RPM installation (provided that it is big enough). This way, all system components, including those installed from RPM repositories, will live on a single drive and not interfere with your personal data (or with your custom installations of applications from ZIP archives) which we recommend to store on a separate partition. Installing the RPM and Unix tree to a sub-folder is not well tested and therefore not yet possible.

Start the WPI installer and carefully follow the on-screen instructions, briefly:

  • When the self-installing WarpIN package finish, you must restart the system to validate the new statements and changes made into configuration files.
  • On the next reboot, let's connect to the Internet, open the command window that was created by the bootstrap yum WarpIN package (now there is a folder on the desktop) and type inside the command 'yum install yum' (which guarantees the installation of the latest updated version available for RPM/YUM for OS/2 and eComStation and simultaneously generating the first Unix-style branch on the root disk selected to install).
  • After installation, the transitional yum bootstrap WarpIN package can be uninstalled, strongly recommended, since the bootstrap basically has a transitional function and uses different paths, libraries and tools that may not be at the same level of the last version available just installed via Internet, also will not be liable in the potential risk of using its console to install other software!
  • At this point you can manage RPM repositories from a command window (read the documentation about it) and start installing the software you desire.

Following ones are the download links for manual installation:

RPM&YUM for OS/2 v. 1.5 (Pentium4, 26/8/2016, Netlabs)
 rpm.netlabs.org/bootstrap/rpm-yum-bootstrap-1_5-p4.wpi
RPM&YUM for OS/2 v. 1.5 (i386, 26/8/2016, Netlabs)
 rpm.netlabs.org/bootstrap/rpm-yum-bootstrap-1_5-i386.wpi
Record updated last time on: 11/11/2019 - 06:20

Translate to...

Comments

Help! I want to automate installation of RPM & YUM for OS/2 by sending keyboard events, so that a virtual machine with OS/2 + Yum can be produced with fully machined Packer instructions. Out of the box, OS/2 comes with the browser "WebExplorer", which is able to download some FTP and HTTP URLs. This helps to get WarpIN installed. However, when I supply the http://rpm.netlabs.org/bootstrap/rpm-yum-bootstrap-1_5-i386.wpi URL, such as saving to "yum.wpi", then WebExplorer appears to silently fail. After several seconds a console check with `dir c:\yum.wpi` reveals the file size is merely 238 bytes, whereas the actual file size is 22 MB. How are OS/2 users supposed to be able to download this file? If wget were installed, we could wget the yum WPI. However, we need yum in order to install wget. It seems there's a chicken and egg situation: Which comes first? The only other built-in download client I have found so far in OS/2 Warp is an `ftp` client, which unfortunately doesn't support HTTP transfers or even much of modern FTP transfers. Is there another built-in download client able to retrieve the RPM & YUM WPI?

First of all, you are better off asking this on a forum like os2world, secondly, only very old versions of OS/2 come with only WebExplorer as the web browsing option, newer versions have Netscape and Firefox etc. Trying to install RPM etc on such an old system that has not been updated etc is bound to fail, you will have to install Fixpack 40 or higher and a few other dependencies before you can hope to install software like RPM that is 25 years younger than the OS version you are trying to install onto.

Add new comment