NAME

App::Pinto::Admin::Command::pin - force a package into the index

VERSION

version 0.030

SYNOPSIS

  pinto-admin --root=/some/dir pin [OPTIONS] PACKAGE_NAME ...
  pinto-admin --root=/some/dir pin [OPTIONS] < LIST_OF_PACKAGE_NAMES

DESCRIPTION

This command pins a package so that it will always appear in the index even if it is not the latest version, or a newer version is subsequently mirrored or imported. You can pin the latest version of the package, or any arbitrary version of the package.

Only one version of a package can be pinned at any one time. If you pin Foo::Bar-1.0, and then later pin <Foo::Bar-2.0>, then Foo::Bar-1.0 immediately becomes unpinned.

To forcibly unpin a package, so that the latest version appears in the index, please see the unpin command.

COMMAND ARGUMENTS

To pin the latest version of a particular package, just give the name of the package. For example:

  Foo::Bar

To pin a particular version of a package, append '-' and the version number to the name. For example:

  Foo::Bar-1.2

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.

COMMAND OPTIONS

--message=MESSAGE

Prepends the MESSAGE to the VCS log message that Pinto generates. This is only relevant if you are using a VCS-based storage mechanism for Pinto.

--nocommit

Prevents Pinto from committing changes in the repository to the VCS after the operation. This is only relevant if you are using a VCS-based storage mechanism. Beware this will leave your working copy out of sync with the VCS. It is up to you to then commit or rollback the changes using your VCS tools directly. Pinto will not commit old changes that were left from a previous operation.

--noinit

Prevents Pinto from pulling/updating the repository from the VCS before the operation. This is only relevant if you are using a VCS-based storage mechanism. This can speed up operations considerably, but should only be used if you *know* that your working copy is up-to-date and you are going to be the only actor touching the Pinto repository within the VCS.

--tag=NAME

Instructs Pinto to tag the head revision of the repository at NAME. This is only relevant if you are using a VCS-based storage mechanism. The syntax of the NAME depends on the type of VCS you are using.

AUTHOR

Jeffrey Ryan Thalhammer <jeff@imaginative-software.com>

COPYRIGHT AND LICENSE

This software is copyright (c) 2011 by Imaginative Software Systems.

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