https://github.com/fedora-modularity/fus
https://github.com/fedora-modularity/fus
Last synced: about 1 year ago
JSON representation
- Host: GitHub
- URL: https://github.com/fedora-modularity/fus
- Owner: fedora-modularity
- License: gpl-3.0
- Created: 2018-06-02T10:37:01.000Z (about 8 years ago)
- Default Branch: master
- Last Pushed: 2023-03-22T09:58:47.000Z (about 3 years ago)
- Last Synced: 2024-04-16T03:57:53.473Z (about 2 years ago)
- Language: C
- Size: 169 KB
- Stars: 6
- Watchers: 5
- Forks: 10
- Open Issues: 8
-
Metadata Files:
- Readme: README.md
- License: COPYING
Awesome Lists containing this project
README
## Purpose
This tool attempts to produce a viable "depsolved" collection of packages.
Unlike earlier tools of this type, it understands the concept of modules and module
streams and can incorporate them into the dependency solving algorithm.
It takes as input a list of repositories and a list of artifacts of various types
that must be in the output package set. The full list of input types is in "Usage"
below, but it includes individual RPMs, comps style groups and categories, and, as
mentioned above, modules, either whole or as part of a stream.
It then attempts to output a package set that includes all required artifacts as well
as all additional packages needed to allow the required artifacts to be installed.
NOTE: This does not mean that the entire output package set can be installed at once.
Many module use cases prevent this, as do some existing basic RPM use cases.
What it does mean is that for each output artifact, there is the potential to resolve
the RPM and module-level dependencies to allow it to install.
## Known limitations
- Shared RPM artifacts are not supported
## Building
```
$ meson builddir
$ ninja -C builddir
```
## Usage
```
$ ./builddir/main --repo NAME,TYPE,PATH --debug ITEM
```
There can be multiple repos. The name is just the name of the repository; type
can be `lookaside` or anything else.
Item to include in the input can have one of the following forms.
* `module(NAME)` or `module(NAME:STREAM)` for modules
* `group:foo` or `category:bar` for comps input
* just package name, or a glob matched against package names
## Testing
To run all the available tests:
```
$ ninja -C builddir test
```
Or to have more control on which tests are run, use `gtester`:
```
$ G_TEST_SRCDIR=$PWD/tests gtester builddir/tests
```