zopencommunity / meta

Meta - Introducing the zopen package manager Meta adds package management facilities to z/OS, via . It is similar to utilities like apt, dpkg, yum, yast2, and emerge. It is written as a pure shell script to remove any prerequisites (like python/perl/bash etc). This package manager is designed for everyday usage of the zopen community ports within the z/OS UNIX environment or for those who wish to download the tools. **Download** the latest zopen package manager here. Pre-config It is advised to have the following set on the system to ensure correct operation: Make sure the character device is untagged or you may experience unexpected behaviour. Run to remove any tags. Installation and sample usage Start with quick start guide. Important usage notes • Remote repositories utilise the suffix - where required, packages should be specified **without** the suffix. For example, using rather than . Root filesystem install • Selecting as the root filesystem will allow the tools to be available system-wide for all users who configure their usage. The install needs to be done by a sysadmin [or someone with sufficient rights using the port for example] as the installer will write files to the tree and configuration information to /etc. There will also be a configuration file written as - this can be sourced by other users. • Removing zopen and the zopen community once installed involves: • Uninstalling all installed packages; removing any copies of • Removing the configured zopen root directory (by default but is set during installation) • Running a command to find any final orphaned symlinks on the system, such as: where is ' ' • Replace with to actually remove symlinks, the example command should only list what was found. • Care should be taken when removing any files with sysadmin authority to prevent removing critical files! Basic command introduction Most commands have extended help available using the parameter. The following usage guidance should be sufficient to get a system running. Used to initialise a zopen community environment. By default, this will create a directory in your directory as the root filesystem (rootfs). The rootfs holds the various packages, configuration files, and environment for zopen community packages. Removing this directory will revert the system without a trace. A Zopen Community main configuration file is generated in . To enable the Zopen Community, this will either need to be sourced after logon to the system or the following line can be added to (or .bash_profile or...) to automatically source the Zopen Community configuration file. It is possible to reinitialize a system using the option - doing so will remove the previous configuration though the rootfs can overlap the old filesystem to reuse installed and/or cached packages for example. Initialisation on a system that has previously had a zopen community configuration should allow some parameters to be copied across, such as Github tokens. Used to install a zopen community package. By default, the latest stable version is installed although options are available to install specific versions, tags or to pick from a selection [see for more]. Used to upgrade zopen community packages. Without parameters, all installed packages will be upgraded; individual packages can be specified on the command line to upgrade only those packages. Packages can be "pinned" to prevent upgrading in case a later release is found to be broken or incompatible - creating a file in the package directory prevents the upgrade; removing the file allows upgrades to occur. Used to remove resources on the system. zopen will retain old versions of packages to allow for switching versions or quick re-installs; downloaded pax files are held in a cache while the specific version files are maintained in the directory configured during initialisation. Using the option removes those unused resources. In addition, zopen utilises symlinks for maintaining the appropriate file structure. Should a problem occur during package installation, removal, or version change, dangling symlinks might be present. The option will (slowly) analyse the rootfs and prune any dangling symlinks. Used to list versions of a package if there are multiple versions present; using the parameter allows for the active version to be changed. Removes a package from the system, leaving the version on the system for re-use later; the directory will also remove the versioned directory, requiring a potential download and/or an unpax to occur to re-install that version.. With no parameters, will list the available packages against the currently installed versions; more usefully, using the parameter lists the actually locally-installed packages rather than all potential packages Searches the remote repository for the specified package, returning appropriate meta-data about the package if found. Queries the local zopen community system. See for more details. Migrating from zopen version <0.8.0 **Note:** The new zopen package manager is not compatible with previous versions of zopen. Migration involves creating a new directory structure for zopen tools. This is accomplished via the command, documented below. Before you migrate • Identify the tools you have already installed. Use . • If you plan to reuse the existing zopen root directory for installing the new tools, then make sure to back it up to a different directory. • Follow the steps below and install each of the tools again via Useful resources • View the zopen community project home: https://github.com/zopencommunity • View the main Meta documentation at https://zopen.community