bdep/0.19.0-a.0.20260427145852.59d6a6e71179

Version 0.18.0

  * Fetch cache and offline mode.

    The fetch cache stores downloaded resources (repository metadata, package
    archives, etc) which are then reused whenever appropriate. This can speed
    up operations like bdep-init substantially. If all the resources are
    cached, then bdep can now be instructed to run offline without making any
    network requests.

    Relevant new options:

    --offline
    --no-fetch-cache
    --fetch-cache <mode>
    --fetch-cache-session

    See bdep-common-options(1) for detail.

  * Ability to use package names in addition to package directories in
    commands other than bdep-init.

    Once a package is initialized, it is now possible to refer to it using
    its name rather than its directory. For example:

    bdep init @gcc -d libfoo -d foo
    bdep ci -d libfoo # Old way (package directory).
    bdep ci libfoo    # New way (package name).

  * Ability to specify negative values for the -j|--jobs option.

    If the value is negative, then the number of available hardware threads
    is reduced by this value.

  * New bdep-ci command --force option that can be used to force the
    submission in the presence of uncommitted changes.

  * The bdep-publish command now publishes all project packages if none are
    specified explicitly.

  * The bdep-publish command now prompts the user to confirm if the alpha
    section is appropriate for a package version 0.X.Y.

  * New --sqlite-synchronous option and BUILD2_SQLITE_SYNCHRONOUS environment
    variable.

    These option and environment variable can be used to set the filesystem
    synchronization mode for the project SQLite database. Note also that the
    WAL (Write-Ahead Logging) journaling mode is now used for the project
    database. See bdep-common-options(1) for detail.

Version 0.17.0

  * New `third-party` library and executable sub-option in bdep-new.

    This sub-option is meant for converting an existing third-party project
    to build2. It automatically enables a number of other sub-options (such
    as no-version, no-readme, and no-symexport). It also adds a number of
    values to manifest that makes sense to specify in a package of a third-
    party project and, unless no-package-readme is specified, generates the
    PACKAGE-README.md template.

  * New buildfile-in-prefix library and executable sub-option in bdep-new.

  * New export-stub executable sub-option in bdep-new.

  * New no-symexport and auto-symexport library sub-options in bdep-new.

  * New no-subdir-include library sub-option in bdep-new.

Version 0.16.0

  * The bdep-deinit command can now deinitialize a package that still has
    dependents.

    In this case, the package is replaced with the closest available version
    from a repository. See also the new --no-fetch option in bdep-deinit(1).

  * New bdep-ci command --target-config and --package-config options to match
    the *-package-config package manifest values.

    Note that the existing --interactive|-i, --builds, and --build-config
    option values have been adjusted as well. See bdep-ci(1) for details.

  * The bdep-new command may now add `type` and `language` values to the newly
    created package manifests.

    These values can help determine the package type (executable, library) and
    language and are used, for example, by bpkg-pkg-bindist to produce correct
    binary distribution packages.

  * New `branch` suboption for the git vcs option in the bdep-new command.

    This suboption can be used to specify the initial branch name in the newly
    created repository.

  * New --sys-* options in the bdep-init and bdep-sync commands.

    This is a subset of the bpkg-pkg-build --sys-* options for controlling
    interaction with the system package manager. See the "System package
    manager query/installation support for Debian and Fedora" NEWS item in
    bpkg for background.

Version 0.15.0

  * Support for JSON output in the bdep-status, bdep-config-list commands.

    See the --stdout-format option in bdep-status(1) and bdep-config(1)
    for details.

  * Support for submitting to a CI server packages with a non-standard
    version.

    See bdep-ci(1) for details.

  * Support for publishing packages with a non-standard version.

    See bdep-publish(1) for details.

Version 0.14.0

  * Support for configuration types, configuration linking, and build-time
    dependencies.

    Configurations can now be linked with each other to allow a package to be
    built in one configuration while its dependencies -- in one or more linked
    configurations. This can be used to create a "base" configuration with
    common dependencies that are shared between multiple configurations.

    Configurations now also have types with the three predefined types being
    `target` (the default) `host` (used for build-time project packages and/or
    dependencies), and `build2` (used for build system modules). We can now
    also have multiple default... More