Automated builds of OSLib (CI)

[Jean-Michel]

In message <mpro.r07rsh02bzy6s01y2.lists at stevefryatt.org.uk>
          Steve Fryatt <lists at stevefryatt.org.uk> wrote:

> On 29 Sep, Justin F wrote in message
>     <alpine.DEB.2.21.2109291956160.2900 at work.gerph.org>:

>> However, this code still exists and trivial though it is, it would allow
>> OSLib to be built and tested automatically on GitHub, and it would mean
>> that it would be possible for people to submit PRs against it, and have
>> them reviewed. I know there's not exactly a glut of change going on with
>> RISC OS or OSLib, but a more modern approach to the management of the
>> sources might mean that it was less maintenance and easier to accept
>> changes...
>> 
>> So is there any interest in that?

> Definitely!

> I'm conscious that the whole subject of source control, and Git especially,
> can be a bit sensitive in the RISC OS world, so I'd not raised the question
> because I don't actively dislike Subversion. However, I'd personally be
> happy to see OSLib move over to Git if that helped automate things at all.

> I'm just one voice of many, however, so what do other people think?
I use OSLib and OSLibSupport (for exceptions) in all of my little programs 
with DDE.
I have version 7.0 of the library.
No problem to use OSLib with CathLibCpp.
All corrections and updates are welcome.

>> At the very least it would be simple to set up a static mirror to allow
>> people to give PRs that can be manually updated using the existing
>> mechanism.

> That's another option, which might be a useful half-way house.


Jean-Michel

-- 
Jean-Michel BRÜCK (France)
Mél :jmc.bruck at orange.fr
Site : https://jeanmichelb.riscos.fr/
RiscOS 5.29 : RiscPc/Raspberry/ARMX6.