txpipe
feat(build): Add Open Build Service support
I am not saying this fixes everything, due to the nature of integration of several services, there may be improvements needed later, but until we merge this and release new version, I won't be able to tell...
We have succeeded where others have failed... =)
https://download.opensuse.org/repositories/home:/CardanoOS:/Factory/openSUSE_Tumbleweed/x86_64/
Moving to milestone v1.2 for now... I hope we can agree that integration for native packages (RPM and DEB) for wide range of distributions is beneficial, but there is no rush...
@mark-stopka I'm in the process of understanding OBS and I have some questions:
- how does the workflow authenticate to OBS? I don't see any credentials or secrets
- seems that the version of the package is hardcoded, would that be automated somehow?
- I see a PERLUR copyright notice, is this a requirement?
@mark-stopka I'm in the process of understanding OBS and I have some questions:
- how does the workflow authenticate to OBS? I don't see any credentials or secrets
If you get your own account, you can use organization secrets to authenticate, I myself now use intermediate GH repository...
- seems that the version of the package is hardcoded, would that be automated somehow?
Yes, there is OBS service that updates the version in the OBS, so that the version in this repository can be constant.
https://github.com/CardanoOS/Factory/blob/050ac9e24512aa71731f254dd2217649d4980ded/packages/oura/_service#L17
- I see a PERLUR copyright notice, is this a requirement?
No, it is something that comes from vim skeleton files for .spec files.
@mark-stopka I'm in the process of understanding OBS and I have some questions:
- how does the workflow authenticate to OBS? I don't see any credentials or secrets
- seems that the version of the package is hardcoded, would that be automated somehow?
- I see a PERLUR copyright notice, is this a requirement?
The copyright notice was changed to TxPipe, is that sufficient?