https://github.com/jimporter/mopack

Multiple origin package management
https://github.com/jimporter/mopack

apt c c-plus-plus conan package-manager pkg-config

Last synced: 2 months ago
JSON representation

Multiple origin package management

• Host: GitHub
• URL: https://github.com/jimporter/mopack
• Owner: jimporter
• License: bsd-3-clause
• Created: 2020-04-01T21:15:24.000Z (over 4 years ago)
• Default Branch: master
• Last Pushed: 2024-09-12T18:50:14.000Z (3 months ago)
• Last Synced: 2024-10-01T10:06:25.764Z (3 months ago)
• Topics: apt, c, c-plus-plus, conan, package-manager, pkg-config
• Language: Python
• Homepage: https://jimporter.github.io/mopack
• Size: 1.99 MB
• Stars: 0
• Watchers: 1
• Forks: 1
• Open Issues: 10
• Metadata Files:
  • Readme: README.md
  • Changelog: CHANGES.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# mopack

[![PyPi version][pypi-image]][pypi-link]

[![Documentation][documentation-image]][documentation-link]

[![Build status][ci-image]][ci-link]

[![Coverage status][codecov-image]][codecov-link]

**mopack** (pronounced "ammopack") is a *multiple origin* package manager, with

an emphasis on C/C++ packages. It's designed to allow users to resolve package

dependencies from multiple package managers ("origins").

## Why mopack?

### Separate abstract and concrete dependencies

Generally speaking, developers of a project are more concerned about

dependencies in the abstract: if your project requires Boost v1.50+, that's all

that really matters. However, when building a project, you work with concrete

dependencies: you naturally have to download a particular version of Boost and

build/install it in a particular way. mopack supports this by letting a

project's build system asking how to use (link to) an abstract dependency, which

mopack will resolve via a particular concrete dependency.

### No configuration necessary

If you've already downloaded and installed a project's dependencies, you usually

don't need to do anything else. mopack can find dependencies using common

methods for the relevant platform (e.g. pkg-config, searching system paths).

### Easy overrides

To simplify building their project, developers can provide a default mopack

configuration so that a standard build just works without any extra effort.

However, people who *build* the project may prefer to resolve packages from

somewhere else. mopack makes this easy: simply pass in an extra mopack file with

new definitions for any dependency, and mopack will use those instead.

## Installation

mopack uses [setuptools][setuptools], so installation is much the same as any

other Python package:

```sh

$ pip install mopack

```

From there, you can start using mopack to build your software!

## License

This project is licensed under the [BSD 3-clause license](LICENSE).

[pypi-image]: https://img.shields.io/pypi/v/mopack.svg

[pypi-link]: https://pypi.python.org/pypi/mopack

[documentation-image]: https://img.shields.io/badge/docs-mopack-blue.svg

[documentation-link]: https://jimporter.github.io/mopack/

[ci-image]: https://github.com/jimporter/mopack/actions/workflows/build.yml/badge.svg

[ci-link]: https://github.com/jimporter/mopack/actions/workflows/build.yml?query=branch%3Amaster

[codecov-image]: https://codecov.io/gh/jimporter/mopack/branch/master/graph/badge.svg

[codecov-link]: https://codecov.io/gh/jimporter/mopack

[setuptools]: https://pythonhosted.org/setuptools/