NAME

App::Pinto::Admin::Command::remove - remove distributions from the repository

VERSION

version 0.029

SYNOPSIS

  pinto-admin --repos=/some/dir remove [OPTIONS] ARCHIVE_PATH ...
  pinto-admin --repos=/some/dir remove [OPTIONS] < LIST_OF_ARCHIVE_PATHS

DESCRIPTION

This command removes a distribution archive and all its packages from the repository and recomputes the 'latest' version of the packages that were in that distribution.

COMMAND ARGUMENTS

Arguments to this command are the paths to the distribution archives you wish to remove. The precise archive that will be removed depends on who you are. So if you are JOE and you ask to remove Foo-1.0.tar.gz then you are really asking to remove J/JO/JOE/Foo-1.0.tar.gz.

To remove an archive that is owned by another author, use the --author option to change your identity. Or you can just explicitly specify the full path of the archive (note that paths are always expressed with forward slashes). So the following two examples are equivalent:

  $> pinto-admin --repos=/some/dir remove --author=SUSAN Foo-1.0.tar.gz
  $> pinto-admin --repos=/some/dir remove S/SU/SUSAN/Foo-1.0.tar.gz

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

--author=NAME

Sets your identity as a distribution author. The NAME can only be alphanumeric characters only (no spaces) and will be forced to uppercase. The default is your username.

--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.

DISCUSSION

Local packages are always considered 'later' then any foreign package with the same name, even if the foreign package has a higher version number. So a foreign package will not become 'latest' until all versions of the local package with that name have been removed.

Removing the latest version of local package generally works as you would expect. That is, the package with the next highest version (if it exists) will take its place in the 02packages.details file. But when removing the latest version of a foreign package, the next 'latest' version may not always appear in the 02packages.details file, or it may not be the version you were expecting.

This is because Pinto does not examine the contents of a foreign distribution, so it only knows about the packages listed in the foreign index. This may not actually represent all the packages in that distribution. Moreover, the completeness of the history of a foreign package depends on how often you update your repository. So if you update infrequently, there may be large gaps between the package versions that your Pinto repository knows about.

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.