Skip to content

About

A conda-smithy repository for libzip.

Resources

Contributing

Stars

0 stars

Watchers

4 watching

Forks

Repository files navigation

About libzip-feedstock

Feedstock license: BSD-3-Clause

Home: https://libzip.org/

Package license: BSD-3-Clause

Summary: A C library for reading, creating, and modifying zip archives.

Development: https://github.com/nih-at/libzip

Documentation: https://libzip.org/documentation/

libzip is a C library for reading, creating, and modifying zip archives. Files can be added from data buffers, files, or compressed data copied directly from other zip archives. Changes made without closing the archive can be reverted. The API is documented by man pages.

Current build status

GitHub Actions
Azure
VariantStatus
osx_64 variant
osx_arm64 variant

Current release info

Name Downloads Version Platforms
Conda Recipe Conda Downloads Conda Version Conda Platforms

Installing libzip

Installing libzip from the conda-forge channel can be achieved by adding conda-forge to your channels with:

conda config --add channels conda-forge
conda config --set channel_priority strict

How to use

With conda
conda install libzip
With mamba
mamba install libzip
With pixi
# for adding to your local project
pixi add libzip
# for installing globally
pixi global install libzip

Search package versions

It is possible to list all of the versions of libzip available on your platform:

With conda
conda search libzip --channel conda-forge
With mamba
mamba search libzip --channel conda-forge
With pixi
pixi search libzip --channel conda-forge
With mamba repoquery, which may provide more information
# Search all versions available on your platform:
mamba repoquery search libzip --channel conda-forge

# List packages depending on `libzip`:
mamba repoquery whoneeds libzip --channel conda-forge

# List dependencies of `libzip`:
mamba repoquery depends libzip --channel conda-forge

About conda-forge

Powered by NumFOCUS

conda-forge is a community-led conda channel of installable packages. In order to provide high-quality builds, the process has been automated into the conda-forge GitHub organization. The conda-forge organization contains one repository for each of the installable packages. Such a repository is known as a feedstock.

A feedstock is made up of a conda recipe (the instructions on what and how to build the package) and the necessary configurations for automatic building using freely available continuous integration services. Thanks to the awesome service provided by Azure, GitHub, CircleCI, AppVeyor, Drone, and TravisCI it is possible to build and upload installable packages to the conda-forge anaconda.org channel for Linux, Windows and OSX respectively.

To manage the continuous integration and simplify feedstock maintenance, conda-smithy has been developed. Using the conda-forge.yml within this repository, it is possible to re-render all of this feedstock's supporting files (e.g. the CI configuration files) with conda smithy rerender.

For more information, please check the conda-forge documentation.

Terminology

feedstock - the conda recipe (raw material), supporting scripts and CI configuration.

conda-smithy - the tool which helps orchestrate the feedstock. Its primary use is in the construction of the CI .yml files and simplify the management of many feedstocks.

conda-forge - the place where the feedstock and smithy live and work to produce the finished article (built conda distributions)

Updating libzip-feedstock

If you would like to improve the libzip recipe or build a new package version, please fork this repository and submit a PR. Upon submission, your changes will be run on the appropriate platforms to give the reviewer an opportunity to confirm that the changes result in a successful build. Once merged, the recipe will be re-built and uploaded automatically to the conda-forge channel, whereupon the built conda packages will be available for everybody to install and use from the conda-forge channel. Note that all branches in the conda-forge/libzip-feedstock are immediately built and any created packages are uploaded, so PRs should be based on branches in forks, and branches in the main repository should only be used to build distinct package versions.

In order to produce a uniquely identifiable distribution:

  • If the version of a package is not being increased, please add or increase the build/number.
  • If the version of a package is being increased, please remember to return the build/number back to 0.

Feedstock Maintainers

About

A conda-smithy repository for libzip.

Resources

Contributing

Stars

0 stars

Watchers

4 watching

Forks

Releases

Sponsor this project

Packages

Used by

Contributors

Languages