App::P...egister(3pm)

💖 App::Pinto::Command::unregister — the manual, but make it make sense 💖

okay bestie, you found yourself in the App::Pinto::Command::unregister page (that's App::P...egister(3pm) if you're reading the header, and it's filed under User Contributed Perl Documentation, iykyk). Buckle up, we're removing packages from a stack and we're gonna look cute doing it. 🎀

---

✨ NAME ✨

App::Pinto::Command::unregister — remove packages from a stack 🧚

---

🌸 VERSION 🌸

version 0.14 — yes she's on 0.14, respect the era 💅

---

🦋 SYNOPSIS 🦋

pinto --root=REPOSITORY_ROOT unregister [OPTIONS] TARGET ...

that's the whole vibe. root, command, options, targets. go off. ✨

---

🔥 DESCRIPTION 🔥

!! THIS COMMAND IS EXPERIMENTAL !! 🚨 like, it works, but it's out here in the wild being experimental, so don't be shocked if it's a little feral.

So what does this actually do? It unregisters packages from a stack, which means they stop showing up in that stack's index. That's it. The archives that hold those packages? They stay in the repository, chillin'. Nothing gets deleted from disk here, okay? 👑

And here's the sister-package tea: when you unregister something, all the sister packages in the same distribution get unregistered too. They move as a unit. It's giving family. It's giving loyalty. 🫶

Now, if you want an archive permanently gone from the repository, that's a whole different girl — use the delete command. And if you want to put packages back on a stack, that's the register command. Don't mix them up, bestie. 😭

---

🎀 COMMAND ARGUMENTS 🎀

The arguments are the targets you want to unregister. A target can be a package (with or without a version number) or a distribution. Like, you have options, and we love that for you. ✨

For example:

Foo::Bar                                 # Unregisters any version of Foo::Bar
Foo::Bar~1.2                             # Unregisters Foo::Bar 1.2 or higher
SHAKESPEARE/King-Lear-1.2.tar.gz         # Unregisters a specific distribuion

(and yes, that last comment says "distribuion" — we keep the source text exactly as it is, typos are part of the lore now 💀)

You can also pipe arguments to this command over STDIN. When you do that, blank lines and lines that look like comments — meaning lines starting with "#" or ';' — get ignored. So go ahead and leave yourself lil notes, she won't read them. 🙈

---

💅 COMMAND OPTIONS 💅

• --diff-style=STYLE — controls the style of the diff reports. STYLE has to be either "concise" or "detailed". Concise reports show only one record for each distribution added or deleted. Detailed reports show one record for every package added or deleted. The default style is "concise". BUT — plot twist — the default style can be changed by setting the "PINTO_DIFF_STYLE" environment variable to your preferred STYLE. And this variable affects the default style for diff reports generated by all other commands too, so it's lowkey a big deal. 🌈
• --dry-run — go through all the motions, but don't actually commit any changes to the repository. Use this to see how the command would potentially impact the stack. It's the "practice run" of options. Look at the fit before you buy it. 👀
• --force — unregister packages even if they are pinned to the stack. ⚠️ Take care when unregistering pinned packages, because it usually means that particular package is important to someone. Like, someone's whole job depends on that package. Be gentle. Be sure. 🥺
• --message=TEXT, -m TEXT — use TEXT as the revision history log message. If you don't use the "--message" option or the "--use-default-message" option, then you'll be prompted to enter the message via your text editor. To control which editor gets used, set the "PINTO_EDITOR" or "EDITOR" or "VISUAL" environment variables. And btw, a log message is not required whenever the "--dry-run" option is set, or if the action didn't yield any changes to the repository. No changes, no essay. periodt. ✍️
• --stack=NAME — unregisters the targets from the stack with the given NAME. Defaults to the name of whichever stack is currently marked as the default stack. Use the stacks command to see the stacks in the repository. Gotta know your stacks before you pick one, fr fr. 📚
• --use-default-message, -M — use the default value for the revision history log message. Pinto will generate a semi-informative log message just based on the command and its arguments. And heads up: if you set an explicit message with "--message", then the "--use-default-message" option gets silently ignored. Not a fight, not a warning, just quietly ignored. 💀

---

👑 AUTHOR 👑

Jeffrey Ryan Thalhammer <jeff@stratopan.com> — the icon behind all this. 🫡

---

🌟 COPYRIGHT AND LICENSE 🌟

This software is copyright (c) 2015 by Jeffrey Ryan Thalhammer.

This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself. 💖

---

and that's the page, bestie — the original was served up by perl v5.40.1 and dated 2025-04-21, and now it's yours. go unregister something responsibly, mwah 💋✨