Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Package management library.

License

NotificationsYou must be signed in to change notification settings

rpm-software-management/libdnf

Repository files navigation

This library provides a high level package-manager. It's core library ofdnf,PackageKit andrpm-ostree. It's replacement for deprecatedhawkey library which it contains inside and useslibrepo under the hood.

⚠️⚠️⚠️Note that DNF4 and libdnf are superseded byDNF5 and libdnf5. DNF5 is the default package manager in Fedora as of Fedora 41. New projects should integrate with libdnf5 instead.⚠️⚠️⚠️

License

LGPLv2+

Building for Fedora

To install build requirements, run following command:

dnf install check-devel cmake cppunit-devel gcc gcc-c++ glib2-devel gtk-doc json-c-devel libmodulemd-devel librepo-devel libsolv-devel libsolv-tools make python2-devel python3-devel python2-sphinx python3-sphinx python2-breathe python3-breathe rpm-devel sqlite-devel swig libsmartcols-devel

From the checkout dir:

mkdir buildcd build/cmake .. -DPYTHON_DESIRED=3make

Building the documentation, from the build/ directory::

make doc

Building RPMs:

tito build --rpm --test

Tests

All unit tests should pass after the build finishes:

cd buildmake test

There are two parts of unit tests: unit tests in C and unit tests in Python. To run the C part of the tests manually, from hawkey checkout::

build/tests/test_main tests/repos/

To manually execute the Python tests, from libdnf git checkout directory::

PYTHONPATH=`readlink -f ./build/src/python/` python3 -m unittest discover -bt python/hawkey/tests/ -s python/hawkey/tests/tests/

The PYTHONPATH is unfortunately needed as the Python test suite needs to know where to import the built hawkey modules.

Contribution

Here's the most direct way to get your work merged into the project.

  1. Fork the project

  2. Clone down your fork

  3. Implement your feature or bug fix and commit changes

  4. If the change fixes a bug atRed Hat bugzilla, or if it is important to the end user, add the following block to the commit message:

    = changelog =msg:           message to be included in the changelogtype:          one of: bugfix/enhancement/security (this field is required when message is present)resolves:      URLs to bugs or issues resolved by this commit (can be specified multiple times)related:       URLs to any related bugs or issues (can be specified multiple times)
    • For example::

      = changelog =msg: Do not close the database if it wasn't openedtype: bugfixresolves: https://bugzilla.redhat.com/show_bug.cgi?id=1761976
    • For your convenience, you can also use git commit template by running the following command in the top-level directory of this project:

      git config commit.template ./.git-commit-template
  5. In a separate commit, add your name and email underLibdnf CONTRIBUTORS section in theauthors file as a reward for your generosity

  6. Push the branch to your fork

  7. Send a pull request for your branch

Please do not create pull requests with translation (.po) file improvements. Fix the translation onFedora Weblate <https://translate.fedoraproject.org/projects/dnf/>_ instead.

Documentation

See thehawkey documentation page.

Information internal to the hawkey development is maintained on agithub wiki.

Useful links

Bug database:


[8]ページ先頭

©2009-2025 Movatter.jp