Closed #577 as completed.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/577#event-10965418970
You are receiving this because you are subscribed to this thread.
Message ID:
___
Rpm-maint mai
As stated above we'd rather not have weak/optional BuildDependencies. Having
predictable builds is a value on it's own. Closing.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/577#issuecomment-1812150848
You are receiving this because
We already have two possibilites how to handle this:
1) DynamicBuildRequies
https://fedoraproject.org/wiki/Changes/DynamicBuildRequires
2) Bootstrap
https://docs.fedoraproject.org/en-US/packaging-guidelines/#bootstrapping
--
You are receiving this because you are subscribed to this thread.
Rep
The issue here is that we do not actually want a weak dependency. The build
should not depend on some package availability in the direct sense. We probably
want to bind the dependency to something more robust.
--
You are receiving this because you are subscribed to this thread.
Reply to this em
There's a use-case here alright, but I've a feeling the solution is something
quite different.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/577#issuecomment-603269558_
> You're basically asking for `BuildRecommends`?
You're referring to ["BuildRecommends
proposal"](https://www.redhat.com/archives/rpm-list/2001-June/msg00193.html).
Thanks for pointing that out.
Indeed, that looks very similar.
There is a difference though: the BuildRecommends tag naming sugge
You're basically asking for `BuildRecommends`?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/577#issuecomment-431722842___
Rp
Say I have a package A build with optional feature B, which depends on package
B:
`BuildRequires: B-devel
`
Now I find out that A doesn't work with B version >= x.
The simplest way to express this is to use:
`BuildRequires: B-devel < x
`
but that makes the build fail for distros that have B >=
