<commit_before>/**
 * @defgroup pkg   Packages
 * @{
 * @brief          External libraries and applications
 *
 * Using packages
 * ==============
 * To add a package to the list of compiled modules you have to add it to the
 * `USEPKG` macro in your application's Makefile. If the package provides
 * header files you might need to update the `INCLUDE` macro, too:
 *
 * ~~~~~~~~ {.mk}
 * USEPKG += <pkg_name>
 * INCLUDE += $(RIOTPKG)/<pkg_name>/...
 * ~~~~~~~~
 *
 * When the package can be build out-of-source, the source code of external
 * packages is fetched in a global location in
 * `$(RIOTBASE)/build/pkg/$(PKG_NAME)`.
 * When out-of-source build is not possible (for example because the package
 * build system doesn't allow it), the source code is fetch in the build
 * directory of the application under `$(BINDIR)/pkg/$(PKG_NAME)`
 * and is the same as the build directory (this is the case for micropython
 * and openthread packages).
 *
 * Porting an external library
 * ===========================
 * Structure of a package
 * ----------------------
 * This module provides porting information for libraries and applications to use
 * with RIOT (to build an external module). If you'd like to add a package to RIOT
 * you need to add a directory with the name of your package to this directory.
 * This directory should contain at least one file:
 *
 *  * **Makefile**: A Makefile describing how to get the upstream application,
 *    apply the patch and how to build the package as a RIOT module.
 *    A rough template for several methods of acquiring a package is provided in
 *    `pkg/Makefile.git` and `pkg/Makefile.http`.
 *
 * Patch files can be included in a `patches` directory in the package dir.
 * These are applied to the upstream package to make it build with RIOT.
 *
 * Creating a patch with git
 * -------------------------
 * Assuming your upstream library resides in a git repository, you can create the
 * patch files as follows:
 *  * checkout the targeted version of the upstream application<commit_msg>pkg/doc.txt: improve rendering of source location documentation<commit_after>/**
 * @defgroup pkg   Packages
 * @{
 * @brief          External libraries and applications
 *
 * Using packages
 * ==============
 * To add a package to the list of compiled modules you have to add it to the
 * `USEPKG` macro in your application's Makefile. If the package provides
 * header files you might need to update the `INCLUDE` macro, too:
 *
 * ~~~~~~~~ {.mk}
 * USEPKG += <pkg_name>
 * INCLUDE += $(RIOTPKG)/<pkg_name>/...
 * ~~~~~~~~
 *
 * When the package can be built out-of-source, the source code of external
 * packages is fetched in a global location in:
 *
 * ~~~~~~~~ {.mk}
 * $(RIOTBASE)/build/pkg/$(PKG_NAME)
 * ~~~~~~~~
 *
 * When out-of-source build is not possible (for example because the package
 * build system doesn't allow it), the source code is fetched in the build
 * directory of the application under:
 *
 * ~~~~~~~~ {.mk}
 * $(BINDIR)/pkg/$(PKG_NAME)
 * ~~~~~~~~
 *
 * In this case, the source and the build directory are the same (currently,
 * this applies to the micropython and openthread packages).
 *
 * Porting an external library
 * ===========================
 * Structure of a package
 * ----------------------
 * This module provides porting information for libraries and applications to use
 * with RIOT (to build an external module). If you'd like to add a package to RIOT
 * you need to add a directory with the name of your package to this directory.
 * This directory should contain at least one file:
 *
 *  * **Makefile**: A Makefile describing how to get the upstream application,
 *    apply the patch and how to build the package as a RIOT module.
 *    A rough template for several methods of acquiring a package is provided in
 *    `pkg/Makefile.git` and `pkg/Makefile.http`.
 *
 * Patch files can be included in a `patches` directory in the package dir.
 * These are applied to the upstream package to make it build with RIOT.
 *
 * Creating a patch with git
 * -------------------------
 * Assuming your upstream library resides in a git repository, you can create the
 * patch files as follows:
 *  * checkout the targeted version of the upstream application
{'fraction_non_alphanumeric': 0.12986094744284704, 'fraction_numerical': 0.0, 'mean_word_length': 3.2955465587044532, 'pattern_counts': {'":': 0, '<': 7, '<?xml version=': 0, '>': 7, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4570545', 'n_tokens_mistral': 1144, 'n_tokens_neox': 1092, 'n_words': 561}