Unplanned carelessness

When i started this site i really didn't think through how to to organize the pages in the content section, i just went along with whatever the theme i was using at the time, in this case: evan.

The result was less than optimal as evan used dates, which is ok if you write one article a day at best, but i write lots of small articles about Void Linux so the organisation was quickly thrown out of the window with weird filenames to be used as tie-breaker for sorting taking its place.

So i decided one day to take the plunge and fix it before it got really out of hand.

Introduction

This is a shorter post, following up on the Loose Ends section of the cross-the-gir.

After dealing with the fallout from merging gir support, there wasn't much to do, glibc-2.29 is still waiting. I decided to take some time to find out why libgusb is failing.

Introduction

For those uninitiated, gir is GObject Introspection. A technology from GNOME that allows libraries to expose bindings to any language that can speak to C. It is the reason you can use lots of languages to write your GNOME and GTK applications while Qt5 is mostly limited to C++ and Python.

On Void Linux a high emphasis is placed into stuff being able to be cross compiled and for a long time gir has eluded us, with it's requirement of running stuff on the target system and using raw dumps of C structures.

Now this is a river that is going to be crossed.

Introduction

Many modern languages (and some old ones) today have their own package manager ecosystem, where someone working on that language can easily get pieces of code written by other people that do their task for them.

A few examples include:

• meta::cpan for Perl.
• PyPi for Python.
• RubyGems for Ruby.
• crates for Rust.

Introduction

This is a follow up on my previous post How this site is done.

Starting as of 2019-02-02 this website now uses a forked version of the even theme for zola (the static site engine for this website).