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

📦
version 0.14000 · 7 versions
, in debian trixie, ubuntu resolute

💖 NAME 💖

App::Pinto::Command::register — okay so basically it puts existing packages on a stack. That's the whole gig. 🫶

✨ VERSION ✨

version 0.14 — yes she's giving 0.14, and she's serving it 🌸

🎀 SYNOPSIS 🎀

pinto --root=REPOSITORY_ROOT register [OPTIONS] ARCHIVE ...

🦋 DESCRIPTION 🦋

!! THIS COMMAND IS EXPERIMENTAL !! 💀

Like, read that again bestie. Experimental. Do with that information what you will 🙈

So what does it do? It adds packages to a stack. The archive that contains those packages must already exist in the repository — that part is non-negotiable, no cap.

Now, if you wanna add packages from an archive sitting in an upstream repository? That's not this command, that's pull. And if you wanna add packages from a local archive? That's add. Don't mix them up, iykyk 💅

🌈 COMMAND ARGUMENTS 🌈

The arguments are the archives you wanna register. You write them like AUTHOR/ARCHIVE_NAME. For example:

SHAKESPEARE/King-Lear-1.2.tar.gz

Periodt. ✨

And ooh, plot twist — you can also pipe arguments into this command over STDIN. When you do that, blank lines get ignored, and so do lines that look like comments (aka lines starting with # or ;). So go ahead and sprinkle your lil notes in there, she'll ignore them 🎀

💅 COMMAND OPTIONS 💅

  • --diff-style=STYLE — this one controls the style of the diff reports, queen of aesthetics. STYLE has to be either concise or detailed. Concise reports show just 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 lowkey you can change that default by setting the PINTO_DIFF_STYLE environment variable to whatever STYLE you prefer. And heads up: that variable affects the default style for diff reports generated by all the other commands too, so it's giving main character energy across the whole repo 👑
  • --dry-run — go through all the motions, but do not actually commit any changes to the repository. Use this when you wanna see how the command would potentially impact the stack. It's the "let me think about it" option, no commitment, we love a situationship 💀
  • --message=TEXT
  • -m TEXT — use TEXT as the revision history log message. But listen: if you don't use --message and you don't use --use-default-message, then you will get prompted to enter the message via your text editor. The editor is controlled by the PINTO_EDITOR or EDITOR or VISUAL environment variables (in that order, bestie, that's the chain). Also — 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. So if nothing happened, no essay required 🫶
  • --stack=NAME
  • -s NAME — registers the targets on the stack with the given NAME. Defaults to the name of whichever stack is currently marked as the default stack. Wanna see what stacks exist in the repository? Run the stacks command, she'll show you around 🌸
  • --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 if you set an explicit message with --message, then the --use-default-message option gets silently ignored. Silently! Not even a text back 😭

👑 AUTHOR 👑

Jeffrey Ryan Thalhammer <jeff@stratopan.com> — thank you for your service, king 🫡

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. Slay, honestly. 🌈

and that's the whole page bestie 💖 this one's from the perl v5.40.1 era, dated 2025-04-21, and it lives under App::P...egister(3pm). go register something iconic ✨🎀🦋

📦 where this page comes from