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

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

💖 NAME 💖

okay so bestie, you've stumbled into the manual for App::Pinto::Command::update — yes, your terminal might file it under App::P...:update(3pm) because it truncates long names like it's got somewhere better to be 🙈. What does it do? It updates packages to the latest versions. That's it, that's the vibe. 💅

🎀 VERSION 🎀

version 0.14 — she's not new new, but she's here and she works. ✨

🦋 SYNOPSIS 🦋

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

look at her go. one line, so much power. 🔥

🌸 DESCRIPTION 🌸

!! THIS COMMAND IS EXPERIMENTAL !! 😭

okay so real talk, this command updates packages in your repository to the newer versions hanging out in an upstream repository. By default, Pinto is lowkey chill about it and just takes the first newer version that it finds — first come, first served, no thoughts head empty. 💀

But if you use the --cascade option, then Pinto gets picky in the best way and will take the newest version it finds among all the upstream repositories. She's shopping around. She's comparing. Iconic behaviour honestly. 👑

💜 COMMAND ARGUMENTS 💜

The arguments are the names of the packages you want to install. But heads up bestie: if you're using the --all or --roots options, then arguments are not allowed. Pick a lane, we can't do both. 🫶

You can also pipe arguments to this command over STDIN. In that case, blank lines and lines that look like comments (i.e. starting with # or ;) will be ignored. Very demure, very mindful. ✨

And if you're using the --all or --roots options, then input will not be read from STDIN. Again: pick a lane. 😌

✨ COMMAND OPTIONS ✨

  • --all — Update all distributions in the stack. We do not attempt to update locally added distributions unless --force is used. If this option is used, then package names cannot be given as command arguments. See also the --roots option. 💫
  • --cascade — !! THIS OPTION IS EXPERIMENTAL !! 😭 When searching for a package (or one of its prerequisites), always take the latest satisfactory version of the package found amongst all the upstream repositories, rather than just taking the first newer version that is found. Remember that Pinto only searches the upstream repositories when the local repository does not already contain a satisfactory version of the package. She checks home first, then she goes shopping. 🛍️
  • --diff-style=STYLE — Controls the style of the diff reports. STYLE must 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. However, the default style can changed by setting the PINTO_DIFF_STYLE environment variable to your preferred STYLE. This variable affects the default style for diff reports generated by all other commands too — so it's not just a this-command thing, it's a whole personality. 🌈

  • --dry-run — Go through all the motions, but do not actually commit any changes to the repository. At the conclusion, a diff showing the changes that would have been made will be displayed. Use this option to see how upgrades would potentially impact the stack. It's the rehearsal, not the performance. 🎭
  • --force — Forcibly unpin any packages that require updating. The pins will not be restored after a succesful update. So like, she's going in whether you like it or not. 💅
  • --no-fail — !! THIS OPTION IS EXPERIMENTAL !! 😭 Normally, failure to pull a target (or its prerequisites) causes the command to immediately abort and rollback the changes to the repository. But if --no-fail is set, then only the changes caused by the failed target (and its prerequisites) will be rolled back and the command will continue processing the remaining targets. 🫡

This option is useful if you want to throw a list of targets into a repository and see which ones are problematic. Once you've fixed the broken ones, you can throw the whole list at the repository again. trial and error but make it efficient. ✨

  • --message=TEXT, -m TEXT — Use TEXT as the revision history log message. If you do not use the --message option or the --use-default-message option, then you will be prompted to enter the message via your text editor. Use the PINTO_EDITOR or EDITOR or VISUAL environment variables to control which editor is used. A log message is not required whenever the --dry-run option is set, or if the action did not yield any changes to the repository. no changes, no essay. 📝
  • --pin — Pins the packages to the stack, so they cannot be changed until you unpin them. Only the packages in the requested targets will be pinned — packages in prerequisites will not be pinned. However, you may pin them separately with the pin command if you so desire. pin what you mean, mean what you pin. 📌
  • --recurse, --no-recurse — Recursively pull any distributions required to satisfy prerequisites for the targets. The default value for this option can be configured in the pinto.ini configuration file for the repository (it is usually set to 1). To disable recursion, use --no-recurse. 🌳
  • --roots — Updates the root distributions of the stack. We do not attempt to update locally added distributions unless --force is used. If this option is used, then package names cannot be given as command arguments. See also the --all option. 🌱
  • --skip-missing-prerequisite=PACKAGE, -k PACKAGE — !! THIS OPTION IS EXPERIMENTAL !! 😭 Skip any prerequisite with name PACKAGE if a satisfactory version cannot be found. However, a warning will be given whenever this occurrs. This option only has effect when recursively fetching prerequisites for the targets (See also the --recurse option). This option can be repeated — stack her up as many times as you need. 🧚
  • --skip-all-missing-prerequisites, -K — !! THIS OPTION IS EXPERIMENTAL !! 😭 Skips all missing prerequisites if a satisfactory version cannot be found. However, a warning will be given whenever this occurrs. This option will silently override the --skip-missing-prerequisite option and only has effect when recursively fetching prerequisites for the targets (See also the --recurse option). she doesn't argue, she just wins. 👑
  • --stack=NAME, -s NAME — Puts all the packages onto 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. 🗂️
  • --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. If you set an explicit message with --message, the --use-default-message option will be silently ignored. okay so that one just doesn't count then, noted. 🤐
  • --with-development-prerequisites, --wd — Also pull development prerequisites so you'll have everything you need to work on those distributions, in the event that you need to patch them in the future. Be aware that most distributions do not actually declare their development prerequisites. so like, pack accordingly, maybe. 🧳

🫶 AUTHOR 🫶

Jeffrey Ryan Thalhammer <jeff@stratopan.com> — the icon, the legend, the one who wrote this. 👑

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. free to share, free to remix, free to slay. ✨

and that's the whole page bestie, no cap, fr fr. this was generated by perl v5.40.1 on 2025-04-21 — go forth and update your packages responsibly, mwah 💋🌈💅

📦 where this page comes from