Add support for Requires/Provides filtering

Open
#35 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
3-5 days
Newbie friendliness
32/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
perl

Research direction

Read the Fedora wiki page linked in the issue for the semantics of the filtering macros, then locate the part of debbuild that generates automatic Requires (and any Provides handling) while processing the spec file. The change is to let a spec supply path and dependency-name filters that are applied before generated entries are written into the control data. Done means a spec with an over-greedy autogenerated dependency list produces a filtered list, and existing spec-parsing tests still pass.

Written by the indexing model from the issue text.

Description

enhancement

Since debbuild is capable of automatically generating dependencies (though it doesn't really do Provides yet), it would be useful to have support for filtering based on the standard filtering macros.

The information about dependency filtering is available on the Fedora Project wiki. Obviously, the Provides filtering is not quite useful right now, since there's no autogeneration of Provides, but being able to send a regex of paths that shouldn't be used to detect dependencies, or what dependencies generated to skip to adding to the list would be incredibly useful.

For example, I have a package that is inexplicably adding automake, autoconf, etc. as dependencies, even though they are only used at build-time. Being able to filter them out would allow for human correction for when the dependency generation gets too greedy.

Dominant language
Perl
Stars
66
Forks
26
Avg merge
26m
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from debbuild/debbuild

All issues in debbuild/debbuild

Similar issues

More Perl issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.