I started messing with Koji a bit again. I've been having a weird issue I can't seem to track down where if I build coreutils I can't build anything else. For whatever reason Koji couldn't find the package despite it being there. This is the sole reason why I decided to take a break from Oela Box for a while. Koji just stopped working correctly one day without any changes to its setup or Oela Box.

I decided to start doing some experimenting. I want to slim down EL development tools to make them a little easier to work with and at the same time hopefully make them more powerful.

Right now I'm getting myself familiar with some of Mock's other features. First I'm learning how building from SCM works in Mock. It's a little tricky and works quite differently from how Koji does it, but I find it fairly interesting.

Next I want to see if I can simulate Koji's tagging system by having a local repository that gets checked for package dependencies first.

#Linux #OpenELA

I have a basic client and server 9P2000 implementation in Julia now. The server only handles 2 messages at the moment. Tversion and Tattach. The client is able to handle any message by using a couple lookup tables. The server uses a couple functions to parse client messages. I want to experiment with making a general purpose IO API, so I can easily adapt the protocol to communicate over stdio. That's where the fun begins since that gets me started with plugin management and RPC.

#Julia #9P2000 #Development

I've got a very simple and easy to use 9P2000 library going in Julia now. On the REPL I'm communicating with a server from Go9p written in Golang.

My library is around 530 lines of Julia. I want the library to be kinda like a "micro library" that's meant to be imported into projects which want to make custom 9P servers and clients.

This may tie into some EL tooling I'm thinking about doing. For right now I'm working toward a plugin management system designed around the protocol.

#Julia #Golang #Development #9P2000

It's pretty neat how much simple flexible tools can be extended. I threw together a few Bash scripts to lookup dependencies for a package, get the names of their sources and auto import them. Oela Importer hasn't been changed at all in order to do this. The scripts are also smart enough not to import a package if it already exists in koji.

#OpenELA #Simple #Flexible #Software

I've been working on a 9P2000 library for Julia as a way to refresh my brain from all the Oela Box work I've been doing. Needed something different to do for a bit to help the creativity and problem solving skills flow.

This is for the most part a translation of another 9P2000 implementation written in Golang. I find it pretty neat how similar Julia and Golang are. A lot of the code requires very few changes to get working.

#9P2000 #Julia #Golang #ProblemSolving

Oela Importer now has a regex mode. Regex mode is disabled by default, but can be enabled using the '-r' flag. I also made the output pretty too.

Also I keep forgetting to announce this. Oela Box now supports Oracle Linux 9.3 as a host!

#OpenELA #python #oracle #linux

I've decided to redesign Oela Importer into a much simpler tool which can be used in Bash scripts. The experimentation I did with parsing gave me the idea to possibly allow regex to be used to match branches against. Theoretically this design will be more flexible and powerful than the last because of its simplicity.

Development notes can be found on this GitHub issue.

https://github.com/maxbyte9p/oelabox/issues/1

#OpenELA #linux #python.

A much nicer directory tree is being put into place for Oela Box. This is just a snippet of it. A majority of the Ansible playbooks and task files have been modified to clean up any cruft. Ansible playbooks prefixed with "role" have been removed and integrated with the provisioning playbooks.

The new tree structure is much more organized than the last and allows greater flexibility compared to the old one.

#OpenELA #ansible

I've written some more documentation for Oela Box. This section goes over the preparation and operation of Oela Box.

#OpenELA #documentation

Now we're getting somewhere. I'm working on doing some rebranding of the Oela Box playbooks. I also want to cut the playbooks down to their bare minimum and remove some unused features.

#OpenELA #linux