On Wednesday, June 22, 2022 7:45:09 PM CEST Kevin Fenzi wrote:
On Wed, Jun 22, 2022 at 11:09:13AM -0000, Michael J Gruber wrote:
> > I also think that every package change (including rebuild) must be
> > tracked in changelog.
>
> I think that convolution is at the very heart of the problem:
>
> As it is, dist-git tracks "packaging sources", i.e. spec and source
hashes
> or files, and this determines the content of the src.rpm and its version.
>
> What you get when you build a binary rpm from that src.spm depends very
> much on the environment. And that environment is not reflected in the
> version nor in the built rpm (besides Build Host and Date).
Well, it's reflected in the requires/provides/contents of the rpm too
though right?
If I build foo-1.0-1 against libbar-2.0-1 and then again against
libbar-4.0-1 its going to require different libs at install/run time.
The problem is that sometimes you build against libbar-4.0-1 vs. libbar-4.0-2
and you get qualitatively different binary RPMs as the result in each case,
despite you triggered both the builds from the same dist-git commit. This
difference is not always reflected in metadata of the resulting RPMs.
Kamil