librepo - A library providing C and Python (libcURL like) API for downloading linux repository metadata and packages

Fedora/Ubuntu name

• check (http://check.sourceforge.net/) - check-devel/check
• cmake (http://www.cmake.org/) - cmake/cmake
• expat (http://expat.sourceforge.net/) - expat-devel/libexpat1-dev
• gcc (http://gcc.gnu.org/) - gcc/gcc
• glib2 (http://developer.gnome.org/glib/) - glib2-devel/libglib2.0-dev
• gpgme (http://www.gnupg.org/) - gpgme-devel/libgpgme11-dev
• libattr (http://www.bestbits.at/acl/) - libattr-devel/libattr1-dev
• libcurl (http://curl.haxx.se/libcurl/) - libcurl-devel/libcurl4-openssl-dev
• openssl (http://www.openssl.org/) - openssl-devel/libssl-dev
• python (http://python.org/) - python2-devel/libpython2.7-dev (python3-devel/libpython3-dev)
• Test requires: pygpgme (https://pypi.python.org/pypi/pygpgme/0.1) - pygpgme/python-gpgme (python3-pygpgme/python3-gpgme)
• Test requires: python-flask (http://flask.pocoo.org/) - python-flask/python-flask
• Test requires: python-nose (https://nose.readthedocs.org/) - python-nose/python-nose (python3-nose)
• Test requires: pyxattr (https://github.com/xattr/xattr) - /pyxattr (python3-pyxattr)

mkdir build
cd build/
cmake ..
make

mkdir build
cd build/
cmake -DPYTHON_DESIRED="3" ..
make

mkdir build
cd build/
cmake -DCMAKE_BUILD_TYPE="DEBUG" ..
make

cd build/
make doc

• C documentation: build/doc/c/html/index.html
• Python documentation: build/doc/python/index.html

https://rpm-software-management.github.com/librepo/

Support for Python 3 is experimental.

Python unittests are not fully working due to missing python3 support in Flask module.

Flask python3 support rely on python3 support in:

• Werkzeug module (Currently - 13.8.2013 - Highly experimental)
• Jinja2 module (Done)
• itsdangerous module (Done)

All unit tests run from librepo checkout dir

make test

build/tests/test_main tests/test_data/

Available params:

• -v Run tests verbosely (Show Librepo debug messages)
• -d Run download tests (This tests need internet connection)

To check memoryleaks:

Add this line to your ~/.bashrc file

alias gvalgrind='G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind'

And then run:

CK_FORK=no gvalgrind --leak-check=full build/tests/test_main tests/test_data/

Suppress known still_reachable memory:

CK_FORK=no gvalgrind --leak-check=full --suppressions=still_reachable.supp build/tests/test_main tests/test_data/

Note: .valgrindrc file is present in checkoutdir, this file contains the settings: --memcheck:leak-check=full --suppressions=./valgrind.supp

PYTHONPATH=`readlink -f ./build/librepo/python/python2/` nosetests -s -v tests/python/tests/

Example of run only one specific test: PYTHONPATH=`readlink -f ./build/librepo/python/python2/` nosetests -s -v tests/python/tests/test_yum_repo_downloading.py:TestCaseYumRepoDownloading.test_download_and_update_repo_01

PYTHONPATH=`readlink -f ./build/librepo/python/python3/` nosetests-3.3 -s -v tests/python/tests/

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 at Red 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 changelog
   type:          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: Decode package URL when using for local filename
     type: bugfix
     resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1817130
     

   • 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 into the authors file as a reward for your generosity

6. Push the branch to your fork

7. Send a pull request for your branch

• Red Hat Bugzilla

• Fedora spec file