GEOPM Service

Edit Package geopm-service
No description set
Source Files
Filename Size Changed
_multibuild 0000000144 144 Bytes
_service 0000001605 1.57 KB
geopm-doc.changes 0000000307 307 Bytes
geopm-doc.spec 0000005980 5.84 KB
geopm-runtime.changes 0000000276 276 Bytes
geopm-runtime.spec 0000003315 3.24 KB
geopm-service.changes 0000000938 938 Bytes
geopm-service.spec 0000007217 7.05 KB
geopmdpy.changes 0000000297 297 Bytes
geopmdpy.spec 0000001680 1.64 KB
geopmpy.changes 0000000329 329 Bytes
geopmpy.spec 0000001533 1.5 KB
Comments 2

Nicolas Morey-Chaisemartin's avatar

One thing I would change in your spec file before submission is the Source and tarball name. It is usually recommended that the Source: is a URL to an upstream tarball. ANd I personally prefer when the tarball contains the Version number. at least we don't risk a bad commit that would unsync tarball and spec.

See: https://build.opensuse.org/package/view_file/science:HPC/openucx/openucx.spec?expand=1

Another solution is to use a _service file that would allow maintainers to download the tarball and the last spec files from your sources at once. See: https://build.opensuse.org/package/view_file/science:HPC/rdma-core/_service?expand=1

But as you have a .spec.in that needs at least a partial build, it might not be the best solution for your case


Christopher Cantalupo's avatar

Thanks for the suggestion! The reason for the version free tarball is a side effect of our CI automation, and I have adjusted the spec file for this submission. For CI we are using a push model with github actions:

https://github.com/geopm/geopm/blob/dev/.github/workflows/build.yml#L118-L135

openSUSE Build Service is sponsored by