RISC OS and full git

Read some posts somewhere about people still using zip files to store intermediate versions of code in development (the 1990s called), and others considering using the RISC OS version of git (simple git ?), which last time I looked was so limited as to be unusable, so thought I’d quickly outline how to make use of the full version of git on RISC OS.

The full version of git (supporting all the utilities and accessing remote repositories over http and ssh) doesn’t yet exist on RISC OS, but it is quite easy to use the Linux version from RISC OS during development.

• Get yourself any Raspberry Pi running Linux, which can be entirely headless if you want.
• Set up a shared directory on the Pi using nfs, samba or even the Linux port of Access
• Inside the shared directory create a git repo using git init
• On RISC OS access the share using Sunfish, Lamman* or ShareFS
• Move your RISC OS source code in to the shared directory
• Using shell on the Linux Pi (!Nettle with a later copy of ssh can be used) to add and commit files
• Optionally set the repo to push to GitLab, GitHub etc

The files stored in git will have the comma extensions for RISC OS specific types, but I think this pretty much how the native version of git is envisioned, so it should be interoperable when the RISC OS full version of git comes along, but any issues should be easily overcome.

Thanks Druck! :)

If users prefer, we have published a complete set of video explaining how to use full git with RISC OS and using different solutions, so for all types of configurations.

Here is more info:

Using Linux git with RISC OS (via a secondary system)

As explained by Druck, link to A video that shows you how-to in few easy steps (video it’s only 10 minutes):

https://www.youtube.com/watch?v=qN5LW6hG7Rk&list=PLEnraaJ9VQfWDl5T4D0P51pG89KRzj0n1&index=4&t=2s

But the devil is into the details!

True, so, if you get an OS that has an up-to-date Samba (which won’t work at this time with RISC OS), here there is a fully detailed article (literally every possible detail), to set up a Samba Server (on any Linux, and in particular on a Raspberry Pi) that will work with ALL your RISC OS systems, included older ones like RISC OS 6, 4.xy and even 3.xy!

https://paolozaino.wordpress.com/2023/03/07/retrocomputing-how-to-build-a-raspberry-pi-server-to-share-files-with-retro-or-vintage-systems-and-modern-platforms-part-1/

Ok, but I don’t want to enable SMB1 on my macOS/linux/windows! It’s dangerous!

Indeed, and on the article above, you’ll quickly notice that it allows you to AVOID having to make your actual daily driver system (macOS, linux and windows) less secure. :)

But what if I do not wish to setup a separate system?

I’m glad you’ve asked! Read below then:

Using macOS git with RISC OS (via RPCEmu, VirtualAcorn, Arculator)

Our super Gerph explains how to use macOS git with RPCEmu. This technique can be also used on MS Windows and Linux with RPCEmu, VirtualAcorn and Arculator! (Exactly in the same way, and always via HostFS).

https://www.youtube.com/watch?v=3RIAktBkslQ&list=PLEnraaJ9VQfWDl5T4D0P51pG89KRzj0n1&index=3

Video roughly just 10 minutes :)

Using git on Windows with RISC OS

Look, I am the last Windows XP user / I have Windows Vista (?1?), 7, 8, 10, 11 and don’t want to use a dirty mac!

No problem! Here we have our amazing Sprow explaining how to use Git Tortoise on Windows and RISC OS, the exact same technique can be used on WIndows and with RPCEmu, VirtualAcorn, Arculator! (So both, windows + a RISC OS computer OR just Windows + emulated RISC OS):

https://www.youtube.com/watch?v=65D1y4RrFA4&list=PLEnraaJ9VQfWDl5T4D0P51pG89KRzj0n1&index=2&t=1s

Video is only 10 minutes, you do not even drink a tea in just 10 minuytes! ;)

But I have no money to buy X, Y and Z!

No worries, all the tools shown in the video above or described by Druck, are all FREE (except where you need to buy a computer of course!).

Still unacceptable for my standards, I only use RISC OS!

Well, as mentioned by Druck, at this very moment, the RISC OS git client is still being developed (although if it’s in a good advanced stage, so probably it’s time to start looking at git anyway!), however, here there is a great video from our talented Cameron that explains how to use !SimpleGit on RISC OS:

https://www.youtube.com/watch?v=v6HWSTVNNeE&list=PLEnraaJ9VQfWDl5T4D0P51pG89KRzj0n1&index=5

Video just 5 minutes! Put your cattle on and enjoy the video ;)

But hear me out, there are reasons to STILL use Linux/Windows and/or macOS with your git repositories even when the RISC OS git client will be released:

Linux, Windows and macOS have:

1) A far more reliable File System, which also allow to recover corrupted data easly
2) Use TRIM on SD/NVMe discs (which help extending their lifespan)
3) They all have good network performances (especially with NFS) and full support for very very large discs
4) You can use free RAID software on Linux
5) They are more secure than RISC OS is

All good reasons to keep your code, your hard work, your creations on those OS instead of only on your RISC OS’s SD card! This is especially true if you’ll decide NOT to use something like GitHub, GitLab public services, because someone out there might be after studying your code :)

Conclusions

There are a ton of options and for every pocket/inclination.

We created some instructional videos for the folks that have very little time. If you need more help, just ask, we’ll be all happy to provide more information if needed, no problem at all, and if you do not wish to ask for help, the videos are out there always ready for you to learn at your discretion and availability (and they are free and not even ADS!)

Hope this helps and best of luck with your coding experience on RISC OS :)

Conclusions
There are a ton of options and for every pocket/inclination.

Right. So zip files it is then. 😋

Linux, Windows and macOS have:

1) A far more reliable File System, which also allow to recover corrupted data easly

The last time I tried to repair a disk on Windows it trashed old the existing folders and left me with 10 of thousands of file fragments instead.

I have viewed the aforementioned videos recently. Absolutely marvellous. They are almost pushing me to just try SimpleGit.

I don’t have a ‘spare’ Linux or Windows machine. I have a MacBook, but I think that’s impossible to connect to with LanManFS. Anyway, I don’t want to have to power that AND the Pi up. I actually do have a small WiFi/Ethernet router on which I installed LEDE. This allows me to plug in a USB flash drive which I can connect to via LanManFS from RISC OS on the Pi. So I get to make backups, meaning I don’t rely on the FileCore-formatted SD card. I can also ssh into the router with Nettle, but I suspect using git on there would be a step too far! :)

You don’t have an old Pi lying around that you no longer use but has refused to die? Even the original 256MB Pi is sufficient, all you need is a 4GB SD card, old phone charger to power it and either an Ethernet cable or a USB WiFi dongle.

The ‘old Pi lying around’ is what I am running RISC OS on. ;) (a Pi1, model B+)

For who has not a “spare” R Pi 1 around, less than 10 quid on eBay:

https://www.ebay.co.uk/itm/134638984166

But, if you do not have even less than 10 quid for a Raspberry Pi 1, you can run Linux on macOS using Docker and read the above info for linux if you do not wish to change the config of your macOS.

Or use docker on Linux and create a very light weight “VM” that doesn’t need the same resoures as a regular Virtual Machine.

And if even this is not viable for you, then don’t worry, just install Linux on your only Pi (so you can have a decent Web Browsing experience and use all the HW on your Pi) and then use RISC OS on RPCEmulator running on top of Linux on your single Pi ;)

There you have it, more viable options :)

@ Rick

Right. So zip files it is then. 😋

XD

I knew you’d say that! :D

Absolutely marvellous.

Thanks Richard! Very much appreciated :)

I switched to writing RISC OS programs using Visual studio code on a pc as it gives a graphical interface for handling git. I store programs on a samba share on an old orangepipc with an external ssd running linux and compile run programs via LanmanFS on a raspberry pi running RISCOS. Visual studio code connects to the orangepipc using ssh. The PC connects to the pi via VNC so I can compile/run code from the pc.

The BIG advantage I found was the ability to see what I had changed from one version to the next easily without using the command line – I can never remember commands.

It sounds complicated but once it is set up I just switch everything on and can program from a pc laptop. I dare say it should work with visual studio code on macos.

It sounds complicated but once it is set up I just switch everything on and can program from a pc laptop.

Indeed, I use Visual Code Studio, which has a ton of plugins for git. But I have a feeling that the folks against git, just don’t know all the advantages, so maybe it’s worth making a video showing some modern UI editing RO code and being fully integrated with git.

Wowsers – I didn’t realise you could pick up a basic Pi for so little money!

I may be a little odd, but it’s compartmentalising things. I have a ‘work’ Windows PC which I use Mon-Fri (it belongs to my employer). I don’t want any personal stuff on there at all. And my MacBook Pro is what I use for browsing the web, shopping etc. All of my RISC OS activity lives on the Pi. When I feel in the mood for some RISC OS messing about, I flick the Pi on. I don’t need to mess about with additional devices. I quite like the idea of the retro-ness of keeping it all within RISC OS.

I think using Visual Studio would be cheating. :). Mind you, I am VERY familiar with it, including the source control integrations, so I suspect I’d be a lot more productive. I do mean to look into how I can configure StrongEd to behave more like Visual Studio. One day…

I suspect that Colin and Paolo are doing it right. Use VS code and enjoy its functionality. My worry is that RISC OS will then feel like work!

I suspect that Colin and Paolo are doing it right. Use VS code and enjoy its functionality. My worry is that RISC OS will then feel like work!

Makes sense, however I do a lot of Open Source stuff too (not even vaguely related to RISC OS or my job), so VSC looks like my tool for everything.

I have a similar situtaion like you, and my employer’s laptop is clean from everything I do not need for work.

In the end, it’s up to you, your personal choice. The point of presenting the options is just to provide multiple ways, and then everyone can pick their favorite or the one that suites their coding workflow better.

I also do a lot of RISC OS coding only on RISC OS itself. I even created my own StrongEd Modes and added tools that make coding with StrongEd more productive. Ultimately, I agree that many times it’s just more fun (and nostalgia) just to use RISC OS on its own. Which is also why on my video of using Git via Linux I use Nettle to connect to my Linux box and so operate only from my RISC OS system.

The other point was to make sure people that read this forum won’t get an opinion (from some over opinionated comment) that git is bad. Nothing wrong with not licking git, but from that to saying it ain’t good, well that’s quite a stretch. And some opinions here may influence people’s choice, making them not having fun, if the only approach “approved” is one that not everyone like.

One of the comment I receive quite often, from the larger RISC OS community (twitter, youtube, FB etc.), is that a lot of comments on this forum seems to imply that certain tools are useles.

One of these tools, for example, is DDT, which, if you watch the videos, you can see it in action and judge by yourself if it’s useful to you or not. In facts, it can be quite useful (as long as someone knows how to use it correctly, which isn’t the case commonly). But, it does have a very outdated UI, which can make it really hard to understand how to use it properly (especially in 2023!).

So, the hope with producing videos, is to show what we have, what we can do with it and how far we can push RISC OS and its tools, without making it a personal war against or in favor of certain tools. As a matter of fact, you’ll never hear things like “this is bad” or “this is better than”. That is left to the viewer, we try to avoid opinions (either over entusiastic or over negative) as much as possible.

Druck wrote

Set up a shared directory on the Pi using nfs, samba or even the Linux port of Access

I’ve never heard of a Linux port of Access. Where can you get that?

Edit: found it!