Skip to content

Releases: gobolinux/ThirdPartyInstallers

RPM boost

05 Jul 00:02
Compare
Choose a tag to compare

This version comes with improved support for RPM. The tool now searches for dependencies on rpmfind and optionally installs them (-d, --install-dependencies). We process both library symbols and program versions when doing a remote search for a dependency.

We no longer symlink packages by default, too. Thanks to GoboLinux' support for filesystem virtualization through Runner we can simply invoke Runner /path/to/program and all dependencies will be activated on the fly.

v2.0: Adjust Makefile to have files under 'Functions' copied when running

03 Jan 15:53
Compare
Choose a tag to compare

This version includes support for the installation of DEB packages. The same features and meta-data created when installing RPM files apply to DEB files too.

Currently the only caveat with DEB files is that there's no easy way to tell the license of a given package. Debian has only recently agreed on a specification for describing that information in a machine-parseable friendly format, but few packages out there use it.

Note that this version has been bumped straight from 1.0 to 2.0 due to a name change in the major script. It is no longer called InstallPackage-RPM but rather just ThirdPartyInstaller (as we may want to include support for further package formats down the road.)

v1.0

02 Jan 03:21
Compare
Choose a tag to compare

All the basic features to support the installation of RPM packages on GoboLinux have been implemented by now, including:

  • Merging multiple RPMs to a single entry on /Programs
  • Flattening /opt under the entry at /Programs and creating compatibility links from /opt back to /Programs
  • Dependencies resolution that includes searches on RPMFind.net, on the GoboLinux recipe store, and on the list of installed programs under /Programs
  • Creation of GoboLinux Resources meta-data such as Architecture, Description, Revision, and UnmanagedFiles

Packages installed by InstallPackage-RPM have an extra meta-data at Resources/PackageSource indicating the original RPM file given as input and the distribution it was generated for (as long as that information is available in the RPM headers).