Sorry forgot that I've already mention about that.
As I wrote I'm using autogenerated from git tag tar balls as input resources to
package geany.
Usually geany-plugins requires the same version of the geany on build stage.
Reason of using that is that with such
In geany-plugins.spec I have line:
```spec
BuildRequires: pkgconfig(geany) >= %{version}
```
to force use exactly the same version of the geany.
Issue is that in generated geany.pc file is "Version: 2.0" so it causes that
geany-plugin build fails because it cannot find `2.0.0` version.
Simple it is a bit unusual skipping that last digit if it is "0".
I have at the moment +5k source packages and literally none of those packages
source code maintainers uses that kind of versioning convention.
IMO simpler would be just keep version and tag the same .. 🤔
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3644#issuecomment-1774232811
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3644/[email protected]>
