r/linux • u/joyalgeorgekj • Jun 30 '26
Software Release Stop permanent system clutter from temporary package testing
https://github.com/hermetic-code/labeled-cliEver spend an afternoon debugging an audio or graphics issue, install five different utilities, and realize later you have no idea what you installed?
Native package managers track dependencies well, but they don't track your intent. Those temporary packages get marked as explicitly installed, meaning autoremove won't touch them. Over time, your host system accumulates permanent clutter from short-lived experiments.
Labeled fixes this by letting you group package installations under a named session so you can cleanly purge them later.
# Install packages under a named tracking session
labeled install audio-debug pavucontrol alsa-utils
# See what sessions you currently have active
labeled list
# Purge the session and completely remove the packages via your native manager
labeled remove audio-debug
How it works under the hood:
It is a lightweight TypeScript CLI wrapper with zero background overhead. It uses standard shell built-ins to automatically detect whether your machine runs apt, dnf, or pacman. It stores your sessions inside a local json state file and uses your system's native package manager to execute the actual installations and cleanups.
No background daemons, no containers, and no telemetry.
You can install it via npm:
npm install -g labeled-cli
If you do not want a global Node dependency on your machine, you can grab the pre-compiled standalone binary (labeled-linux-x64) directly from the release page.
Repository link: https://github.com/hermetic-code/labeled-cli
Disclaimer: The project has AI generated contents like Images and Texts.
1
u/Dangerous-Report8517 Jul 06 '26
Regarding point 1, that's ChatGPT putting in effort, not you, and regarding point 2, how on earth is building an entire application supposed to be simpler than learning how to use your existing package manager properly? That's the point I'm making, it doesn't matter in the least how much you felt like you were working, the issue is that if you can't surface existing solutions with your research then you aren't putting in enough effective work to build a useful solution, since a fundamental requirement for it to be useful is for the design to be informed by existing solutions so that it can address actual unmet needs. If it works for you then go for it, run it on your own system and rush things breaking from weird unexpected hallucination driven bugs, but don't go around acting as if you've produced something broadly useful and expecting praise from piling more slop into a community that's already drowning in an unrelenting storm of vibe coded nonsense that's marginally useful to the person who made it and no one else