Conary (package manager)
It is proposed that this article be deleted because of the following concern:
If you can address this concern by improving, copyediting, sourcing, renaming, or merging the page, please and do so. You may remove this message if you improve the article or otherwise object to deletion for any reason. Although not required, you are encouraged to explain why you object to the deletion, either in your edit summary or on the talk page. If this template is removed, do not replace it. The article may be deleted if this message remains in place for seven days, i.e., after 07:40, 27 March 2022 (UTC). Find sources: – · · · scholar · JSTOR Nominator: Please consider notifying the author/project: {{subst:proposed deletion notify|Conary (package manager)|concern=Not notable. There are no independent sources}} ~~~~ |
 Screenshot of Conary running in a terminal | |
| Initial release | July 15, 2004 |
|---|---|
| Stable release | 2.5.9[1]
/ 3 March 2016 |
| Repository | |
| Written in | Python |
| Operating system | Linux |
| Platform | IA-32, x86-64 |
| Available in | English |
| Type | Package management system |
| License | Apache License, Version 2.0[2] |
| Website | github |
Conary is a free software package management system created by rPath (now SAS) and distributed under the terms of the Apache License Version 2.0. It was relicensed from the GPLv3 in 2013.[2] It focuses on installing packages through automated dependency resolution against distributed online repositories, and providing a concise and easy-to-use Python-based description language to specify how to build a package. It is used by Foresight Linux and rPath Linux.
Conary updates only those specific files in packages which need to be updated; this behavior minimizes bandwidth and time requirements for updating software packages. Conary also features rollbacks[3][4] of package installation as well as derived packages.[5]
The Conary toolchain includes rmake, a build server for conary packages, which builds packages inside chroot environments containing only the package's explicitly listed build requirements and some other fundamental packages. This is very useful for packagers, because it means that package builds can be done inside a reproducible environment, and packagers cannot accidentally introduce dependencies on peculiarities of their machine's environment (such as custom configuration files, or undocumented extra packages).
See also[]
- Foresight Linux
- rPath
- SAS
References[]
- ^ "Release 2.5.9". 3 March 2016. Retrieved 20 July 2018.
- ^ a b Relicense under Apache License version 2.0 from the GPLv3. The change in license was implemented on Sep 1 2013.
- ^ "Rollback, a barrel of fun". Archived from the original on 2012-03-30. Retrieved 2011-08-17.
- ^ Evaluate Conary (Project conary-eval WebHome
- ^ ewtroan: Derived Packages Archived 2007-07-05 at the Wayback Machine
External links[]
| dpkg | |
|---|---|
| RPM | |
| Embedded systems | |
| Distribution-agnostic | |
| Others (binary) | |
| Others (source) |
|
| Front-ends | |
| Related topics |
|
- Free package management systems
- Free software programmed in Python
- Linux package management-related software
- Linux-only free software
- Software using the Apache license