(merge Features/Hawkey into Features/DNF) |
|||
Line 4: | Line 4: | ||
<!-- The actual name of your feature page should look something like: Features/YourFeatureName. This keeps all features in the same namespace --> | <!-- The actual name of your feature page should look something like: Features/YourFeatureName. This keeps all features in the same namespace --> | ||
= DNF, a | = DNF and hawkey, a New Package Manager and Package Management Library = | ||
== Summary == | == Summary == | ||
Provide hawkey, a new package management library built on top of [https://github.com/openSUSE/libsolv libsolv]. Preview the next-generation Yum package manager, using hawkey/libsolv for backend. | |||
== Owner == | == Owner == | ||
Line 19: | Line 19: | ||
* Percentage of completion: 40% | * Percentage of completion: 40% | ||
== Detailed Description == | |||
[https://github.com/akozumpl/hawkey hawkey] is a library allowing clients to query and resolve dependencies of RPM packages based on the current state of RPMDB and yum repositories. While a superset of the functionality itself is available in yum, the new API promises to bring unification, fewer restrictions on clients' implementation language (yum API is in Python) and eventually performance improvements. | |||
The API version of hawkey in Fedora 18 will not be final one, it will more be to demonstrate the concepts of the library. Projects needing depsolving in Fedora will be encouraged to start experimenting and reporting bugs and missing features. | |||
DNF is a fork of Yum 3.4 that uses libsolv for a backed. The main goals of the project are: | |||
DNF is a fork of Yum 3.4 that uses libsolv via hawkey for a backed. The main goals of the project are: | |||
* using a SAT solver for dependency resolving | * using a SAT solver for dependency resolving | ||
** allowing us to eventually use the same solver in rpm too | ** allowing us to eventually use the same solver in rpm too | ||
Line 32: | Line 34: | ||
For Fedora 18 this is mainly meant as a preview. The package can be installed along yum so user's workflow is not disturbed when DNF malfunctions. The users will be advised against using DNF on critical production machines. | For Fedora 18 this is mainly meant as a preview. The package can be installed along yum so user's workflow is not disturbed when DNF malfunctions. The users will be advised against using DNF on critical production machines. | ||
=== Naming === | |||
Note about the name "DNF": it has no relevant meaning, originally meant as a project name only. It is possible to replace this however it would be very difficult to stay with 'yum' as the python package names would clash then. | |||
Note about the name: it has no relevant meaning, originally meant as a project name only. | |||
=== Why not zif/zypp? === | === Why not zif/zypp? === | ||
Line 43: | Line 44: | ||
== Benefit to Fedora == | == Benefit to Fedora == | ||
Faster and simpler package manager. | |||
Hawkey clients will get: | |||
* easier bindings to other languages than Python | |||
* concise, clear package management API | |||
* better performance (through utilizing libsolv) | |||
The set of possible hawkey API consumers: | |||
* dnf (the next generation yum) | |||
* release engineering [https://github.com/akozumpl/hawkey/wiki/Use-cases tools] | |||
* PackageKit | |||
* graphical package management tools | |||
* Anaconda | |||
DNF clients and users will get: | |||
* Faster and simpler package manager. | |||
* Simplified client code. | |||
== Scope == | == Scope == | ||
=== Including libsolv in Fedora === | |||
This is a library for fast dependencies resolving created and maintained by SUSE. The rpms are in Fedora already, we will need to rebase the package as needed. | |||
=== hawkey package === | |||
Including documentation for the API. | |||
=== How To Test === | === How To Test === | ||
Line 62: | Line 84: | ||
--> | --> | ||
Unit tests included | Unit tests included for: | ||
* hawkey C API | |||
* hawkey Python bindings | |||
* DNF | |||
Manual testing is done by performing actions one would normally do through yum, e.g. 'dnf install virt-manager'. | Manual testing is done by performing actions one would normally do through yum, e.g. 'dnf install virt-manager'. | ||
Line 68: | Line 93: | ||
== User Experience == | == User Experience == | ||
=== Hawkey User Experience === | |||
None visible (hawkey is a new library). | |||
=== DNF User Experience === | |||
To test-drive dnf use 'dnf <command>' instead of 'yum <command>'. list/update/install/erase are currently all supported. | To test-drive dnf use 'dnf <command>' instead of 'yum <command>'. list/update/install/erase are currently all supported. | ||
<!-- If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --> | <!-- If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --> | ||
Line 75: | Line 103: | ||
<!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel feature)? --> | <!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel feature)? --> | ||
Hawkey is a new library and will be only depended on by DNF at this point. | |||
DNF will not disturb any existing Fedora software. | |||
In the future if DNF gets accepted as the main package manager of the platform, yum plugins will have to be updated for the new API and so will Anaconda. I am prepared to assist in this effort with documentation and patches. | In the future if DNF gets accepted as the main package manager of the platform, yum plugins will have to be updated for the new API and so will Anaconda. I am prepared to assist in this effort with documentation and patches. |
Revision as of 08:20, 19 June 2012
DNF and hawkey, a New Package Manager and Package Management Library
Summary
Provide hawkey, a new package management library built on top of libsolv. Preview the next-generation Yum package manager, using hawkey/libsolv for backend.
Owner
- Name: Aleš Kozumplík
- Email: akozumpl@redhat.com
Current status
- Targeted release: Fedora 18
- Last updated: 2012-06-19
- Percentage of completion: 40%
Detailed Description
hawkey is a library allowing clients to query and resolve dependencies of RPM packages based on the current state of RPMDB and yum repositories. While a superset of the functionality itself is available in yum, the new API promises to bring unification, fewer restrictions on clients' implementation language (yum API is in Python) and eventually performance improvements.
The API version of hawkey in Fedora 18 will not be final one, it will more be to demonstrate the concepts of the library. Projects needing depsolving in Fedora will be encouraged to start experimenting and reporting bugs and missing features.
DNF is a fork of Yum 3.4 that uses libsolv via hawkey for a backed. The main goals of the project are:
- using a SAT solver for dependency resolving
- allowing us to eventually use the same solver in rpm too
- strict API definition for plugins
- strict API definition for extending projects (Anaconda)
- leaner codebase than Yum, allowing for easier maintenance
- better performance and memory footprint.
For Fedora 18 this is mainly meant as a preview. The package can be installed along yum so user's workflow is not disturbed when DNF malfunctions. The users will be advised against using DNF on critical production machines.
Naming
Note about the name "DNF": it has no relevant meaning, originally meant as a project name only. It is possible to replace this however it would be very difficult to stay with 'yum' as the python package names would clash then.
Why not zif/zypp?
People are asking why we didn't choose to adopt zif (or SUSE's zypp) instead of fixing yum. The reasons are:
- dnf looks for a middle ground between a sane API and some backwards compatibility.
- dnf and hawkey are first steps toward using the same resolver accross the entire stack.
- Libsolv is a well tested and proven code base, currently the most sophisticated and optimized dependency solving implementation.
Benefit to Fedora
Hawkey clients will get:
- easier bindings to other languages than Python
- concise, clear package management API
- better performance (through utilizing libsolv)
The set of possible hawkey API consumers:
- dnf (the next generation yum)
- release engineering tools
- PackageKit
- graphical package management tools
- Anaconda
DNF clients and users will get:
- Faster and simpler package manager.
- Simplified client code.
Scope
Including libsolv in Fedora
This is a library for fast dependencies resolving created and maintained by SUSE. The rpms are in Fedora already, we will need to rebase the package as needed.
hawkey package
Including documentation for the API.
How To Test
Unit tests included for:
- hawkey C API
- hawkey Python bindings
- DNF
Manual testing is done by performing actions one would normally do through yum, e.g. 'dnf install virt-manager'.
User Experience
Hawkey User Experience
None visible (hawkey is a new library).
DNF User Experience
To test-drive dnf use 'dnf <command>' instead of 'yum <command>'. list/update/install/erase are currently all supported.
Dependencies
Hawkey is a new library and will be only depended on by DNF at this point.
DNF will not disturb any existing Fedora software.
In the future if DNF gets accepted as the main package manager of the platform, yum plugins will have to be updated for the new API and so will Anaconda. I am prepared to assist in this effort with documentation and patches.
Contingency Plan
If DNF doesn't work the user can use yum instead.
Documentation
Maintained at github wiki.
Release Notes
None yet.
Comments and Discussion
None yet.