On Sat, 2005-05-21 at 16:24 +0200, Thomas Vander Stichele wrote:
> What's a case where this would be used? Ie, you want to tie the package
> you're building to a _specific_ version of python?
No, you want your spec to build on dists *without* knowing what the
version is, ie without tieing it to a specific version.
What does this solve? The build requirement (as written to the src rpm)
then becomes "if by some coincidence this srpm built with this other
package installed, dissalow rebuilds except against the current version
of that package".
And even that doesn't really guarantee anything, because it was probably
built with "-bs", so it didn't even see if the build *worked* to get
Every time this gets brought up, people use this example to justify it.
I agree that there are packages that _have_ this stuff in them
(obviously), but I still haven't seen a good explanation of how the
example isn't completely contrived.