For what it's worth, when I was doing releases, I built RPMs as well as macOS installer disk images.
Perhaps what can be done is to add recipes for Windows installer, .DMG, RPM, and DEB packages to the build process, and then they can be run by interested parties as needed.
I haven't tried building on macOS in years. I need to look at that again. But I will *NOT* use Homebrew or the like; they cause far too many unnecessary dependencies to be pulled in.
On Fri, Dec 31, 2021 at 11:55 PM Fish Fish <david.b.trout@...> wrote:
Mark A. Stevens wrote:
[...]
> I know enough about RPMs to get myself in lots of trouble,
> so I will point you to some online help. From my experience,
> a part of the team developing a package, builds and tests
> the RPMs.
<snip>
From the sounds of it then, it is not necessarily the developers of the product itself that is necessarily responsible for creating distribution packages, but another team altogether.
I cannot speak for the rest of the team of course, but as for me I'm happy with the way things are.
If someone (or several someones) wants to take on the added responsibility of creating official distribution packages for SDL Hyperion Hercules, they are free to do so. But as for me, I've already got enough on my plate.
--
"Fish" (David B. Trout)
Software Development Laboratories
