tda

Yeah it’s literally just a Rust program that prints “TheDarkArtist” to the console. That’s it. That’s the whole program.

But that’s not the point.

The point

The point was getting something into the AUR. The Arch User Repository is where Arch Linux users share packages, and i wanted to understand the entire pipeline – writing a PKGBUILD, submitting to the AUR, making it installable via yay.

yay -S tda

That command works. My package. In the AUR. For anyone on Arch to install.

What i learned

• PKGBUILD files: How Arch packages are defined – source URLs, build functions, checksums
• makepkg: Building packages locally before submitting
• AUR submission: SSH keys, git remote setup, the .SRCINFO file
• Versioning: How AUR handles updates and version bumps

The actual Rust code is like 5 lines. The packaging knowledge is what matters. And that’s exactly what i took into ipclip – a Rust CLI that actually does something useful, also published on the AUR.

Think of this as the “hello world” of package distribution. Everyone writes a hello world program. Not everyone publishes it to a package repository.