Understanding the automatic provides

2021-07-28 Thread Link Dupont
I noticed that a package I recently submitted (golang-sr-spc-log) has some odd Provides: values. I can't figure out how they're getting generated this way, or why. From the build log[1]: Provides: golang(git.sr.ht/~spc/go-log/go-log-0.1.0) = 0.1.0-1.fc34 [...] Why is the package version (0.1.0)

Re: Understanding the automatic provides

2021-07-28 Thread Link Dupont
For posterity, it seems that in order for git.sr.ht-based forge sources to work correctly, the %topdir macro needs to be defined too. That fixed the strange Provides: and fixed the installation path of the source files into /usr/share/gocode. ___ golan

Re: Understanding the automatic provides

2021-07-28 Thread Elliott Sales de Andrade
On Wed, 28 Jul 2021 at 12:56, Link Dupont wrote: > > I noticed that a package I recently submitted (golang-sr-spc-log) has some > odd Provides: values. I can't figure out how they're getting generated this > way, or why. From the build log[1]: > > Provides: golang(git.sr.ht/~spc/go-log/go-log-0.

Re: Understanding the automatic provides

2021-07-28 Thread Link Dupont
On Wed, Jul 28 2021 at 06:40:01 PM -0400, Elliott Sales de Andrade wrote: It seems you've figured out what you needed, but for clarity, those files are parsed and called from RPM directly: http://rpm.org/user_doc/dependency_generators.html Oh interesting. So to affect the call to %__go_provide