Add support for Requires/Provides filtering
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
- Domain
- build-system, tooling
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
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from debbuild/debbuild
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Pick up flags from dpkg-buildflagsMay be free again @Conan-Kudo claimed this 1044 days ago, and no pull request is open. Open
All issues in debbuild/debbuild
Similar issues
-
Dev-output directory preparation accepts file-valued lib/include paths and fails on dangling linksOpenteam-cli
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 93/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
inverse-inc/packetfence#9728 ·
Maintainers usually reply within 1 day
-
area:cpan-port bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
fglock/PerlOnJava#2153 ·
Maintainers usually reply within 1 day
-
fix(char-create): show the real reason a character is refusedPossibly taken @baphomello claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day