Adding new modules to OSLib

[Justin F]

On Thu, 30 Sep 2021, W P Blatchley via oslib-user wrote:

> On 29/09/2021 21:56, Steve Fryatt wrote:
> 
> > On 29 Sep, Justin F wrote in message
> >      <alpine.DEB.2.21.2109291938270.2900 at work.gerph.org>:
> > 
> > > Or maybe how to submit them?
> > >    - I guess send them to this mailing list and the maintainer will get
> > >      around to it. This is a low traffic list, and there's usually some
> > > lag
> > >      in getting replies because it's not anyone's even part time job :-)
> > Pretty much this -- from my point of view, at least... :-)
> > 
> > Unfortunately real life has been getting in the way of RISC OS stuff a lot
> > for me lately, but I do have a record of the posts to this list that I don't
> > think have been actioned yet and still plan to pick them up as soon as I can
> > if no-one else gets there first.
> 
> Many thanks Justin and Steve. I was talking about adding new modules to the
> source.
> So yes, I guess I'll look at the existing def files and modify until I have
> what I need.
> If I add a new def file to the User directory, will it automatically be picked
> up and
> included in a build?

Ick, sorry that's where my knowledge runs out I'm afraid.

> Personally I think anything that makes OSLib more maintainable is a good
> thing.
> I'm a bit wary of GitHub still because I like to develop on RISC OS alone and
> it
> means I have to use another OS at the moment to check in/out sources. But
> that's
> going to change once the RO git client is finished. So I would support a move
> to GitHub or ROOL's GitLab.

ROOLs is for the OS, whereas having an external service like GitHub serve 
things is more accessible. Plus GitHub can do automation for users without 
any cost or setup hassles.

> I think there's already a version of OSLib in ROOL's GitLab, isn't there?
> Probably because a specific one is needed for something in the RISC OS build
> system. If that could be brought up to date with the latest OSLib and hence
> have a single incarnation of OSLib, that would be ideal I guess.

Unless they've upgraded it, it's based on a very ancient version. The 
problem is that many of the internal components rely on the old OSLib, so 
validating that everything still worked was non-trivial. Especially as 
most of RISC OS has no tests to confirm that things are still working.
At least that was my experience with ROL, and I suspect that they have the 
same experience.

But having it autobuilt is definitely a step in the right direction for 
making it more accessible to all.

-- 
Charles Justin Ferguson
[ All information, speculation, opinion or data within, or attached to,
  this email is private and confidential. Such content may not be
  disclosed to third parties, or a public forum, without explicit
  permission being granted. ]