oWtE.

My first aur repo.

Maybe my last as well.

Diving Into Arch With No Clue

I jumped into Arch Linux with zero idea what I was doing. No roadmap, no hand-holding—just me and the terminal. I told myself I’d daily drive it. Sink or swim. And at first, it felt like drowning.

Broken configs. Missing packages. Endless updates. Every day was a new puzzle. But that’s what made Arch different: it forces you to learn.

Discovering the AUR

Then I stumbled upon the AUR (Arch User Repository). It felt like unlocking a hidden level. Suddenly, Arch wasn’t just about installing what others had made. It was about building, shaping, and contributing.

And that’s when the idea hit me—what if I could put my own app there?

Wrestling With PKGBUILD

I had an Electron app image. No clue how to turn it into a package. So I opened the Electron docs. Found some random guy’s PKGBUILD on GitHub. Copied. Tweaked. Failed.

Over and over.

Missing dependencies. Wrong paths. Broken installs. Every error felt like the system was laughing at me. But with each failure, I learned. Slowly, painfully, the puzzle started to make sense.

The Moment It Worked

After countless retries, I ran the build again. This time, no red errors. Installed clean. Launched smooth.

My first AUR package.

It was more than just code running—it was proof. Proof that I could bend Arch to my will. Proof that struggle builds weight.

Why It Mattered

Arch taught me this:

• Light wins come fast but vanish fast.
• Heavy wins shape you.

And that first AUR package? It was heavy. It carried all my failed attempts, all the frustration, all the learning.

In that moment, I wasn’t just using Arch.
I became someone who could create for it.