You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[yes ] Have you checked for an existing issue describing your idea?
What is your proposal?
PRIORITY_BOOST is package name based but Dry Run output is origin based. Being able to generate a package-name based list that could be extracted and substituted into PRIORITY_BOOST in a poudriere.conf would be handy.
What is the existing behavior, if any?
No part of the Dry Run output is in a form substitutable into PRIORITY_BOOST if extracted.
What is the motivation / use case for the change?
I was trying to have an efficient way to PRIORITY_BOOST all the packages needed to build a specific package (or set of packages).
Did you consider any alternatives?
I'm not aware of a way to have poudriere produce a Package Name based list of what would need to be built.
Is this really a ports feature request?
PRIORITY_BOOST is poudriere specific in the first place and poudirere computes the build-dependency information and already presents it in an origin based form.
Example
It is just having a way to specify to list package names instead of listing origins, such that extracted text would be ready for substitution into PRIORITY_BOOST.
Additional context
One could imagine substituting into other package-name based lists in a poudriere.conf .