New in version 2.8
November 13th, 2014
- 0install gained support for source dependencies (where one program depends on the source code to another).
- The OPAM OCaml package manager is now available through 0install.
New in version 2.6 (January 21st, 2014)
- 0install 2.6 completes the transition from Python to OCaml. There is no remaining Python code in 0install and, therefore, no need to have Python installed in order to build or run it. However, there are some problems using the GTK plugin on OS X - see the thread for details. There's also another blog post in my series for people wanting to get up to speed on OCaml: Polymorphism for Beginners.
New in version 2.0 (March 6th, 2013)
- This version enhances the XML package metadata syntax, allowing more precise specification of dependencies.
- Support for using distribution-provided packages as dependencies has been extended and now covers Arch Linux, Cygwin, Darwin, Debian, Fink, FreeBSD Ports, Gentoo, MacPorts, Mint, openSUSE, Red Hat, Slackware, and Windows.
- The 0install software now supports apps, an easier way to manage 0install applications, improved diagnostics when no compatible versions can be selected, improved usability, and better support for use on headless servers.
New in version 1.16 (February 28th, 2013)
- Running an app when some previously selected packages are no longer present now forces an update in the foreground.
- Arch-style Java version numbers are now supported.
- The Makefile now copes with Arch's Python naming.
- Various minor bugs were fixed.
- This is a 2.0 release candidate.
New in version 1.15 (February 14th, 2013)
- Requirements can now be restricted to a particular distribution, allowing e.g. MacPorts Python libraries to specify that they work only with MacPorts Python.
- Environment variables can be expanded into multiple arguments, which is useful for passing options. .NET Framework installations are now detected on Windows.
- The diagnostics displayed when no selection is possible have been further improved to show the restrictions that prevented the selection of each candidate.
New in version 1.13 (November 10th, 2012)
- We have added much improved solver diagnostics to 0install - instead of just telling you which components it failed to select, it now explains why none of the versions was suitable. 0install 1.12.1 for Windows was released, bringing over several new features from the pure-Python version and fixing a number of bugs. Discussion about ABI annotations (e.g. for C++ programs) continued on the list.
New in version 1.12 (September 26th, 2012)
- Support was added for OS-specific dependencies (e.g. for dependencies only needed on Windows) and for constraints in native package implementations (e.g. Debian's python3-gi package cannot be used with Python 2).
- "0install man" allows the man command to work with 0install applications.
- "0install digest" now has an option to display the manifest.
- A bug in the PackageKit support which meant it sometimes failed to detect candidate packages was fixed.
New in version 1.10 (July 27th, 2012)
- This version adds support for Python 3, PyGObject, and GTK 3 (while continuing to support Python 2, PyGTK, and GTK 2).
- A new directory naming scheme supports cmake and other programs which can't cope with "=" characters in pathnames.
- The new element allows adding version constraints without creating a dependency.
- The new recipe step allows renaming files and directories when unpacking. Various minor bugs have been fixed.
New in version 1.6 (February 13th, 2012)
- Arch Linux native packages can now be used as dependencies.
- "0install update" informs the user if a newer version exists but was not selected for some reason.
- A workaround was added for Python's lack of SSL hostname checking.
- Various minor bugs were fixed.