Pathname for user-choices

• Documentation
• Project

Description

Pathname for the user-choices command-line argument parser allows choices to be automatically converted to Pathname objects.

Features / Problems

This project tries to conform to:

• Semantic Versioning (2.0.0)
• Ruby Packaging Standard (0.5-draft)
• Ruby Style Guide
• Gem Packaging: Best Practices

Additional facts:

• Written purely in Ruby.
• Documented with YARD.
• Automatically testable through RSpec.
• Intended to be used with Ruby 1.9.3 or higher.
• Cryptographically signed gem and git tags.
• This library was developed as part of the Spaces project.

Synopsis

This documentation defines the public interface of the software. Don't rely on elements marked as private. Those should be hidden in the documentation by default.

Loading

In most cases you want to load the library by the following command:

require 'user-choices-pathname'

In a bundler Gemfile you should use the following:

gem 'user-choices-pathname'

Usage

Just like the other types that are supported by user-choices by default you can define a choice to be of the type pathname like the following:

class SomeCommand < UserChoices::Command

  …

  def add_choices(builder)
    …
    builder.add_choice(:somepath, :type => :pathname)
    …
  end

  …

end

When the command is run, arguments given for the choice 'somepath' are then automatically made into Pathname objects and are accessible through the arguments hash stored in the @user_choices instance variable.

The conversion is also able to convert argument lists to Arrays of Pathnames.

Requirements

• Ruby 1.9.3 or higher
• user-choices

Installation

On *nix systems you may need to prefix the command with sudo to get root privileges.

High security (recommended)

There is a high security installation option available through rubygems. It is highly recommended over the normal installation, although it may be a bit less comfortable. To use the installation method, you will need my gem signing public key, which I use for cryptographic signatures on all my gems.

Add the key to your rubygems' trusted certificates by the following command:

gem cert --add aef-gem.pem

Now you can install the gem while automatically verifying its signature by the following command:

gem install user-choices-pathname -P HighSecurity

Please notice that you may need other keys for dependent libraries, so you may have to install dependencies manually.

Normal

gem install user-choices-pathname

Automated testing

Go into the root directory of the installed gem and run the following command to fetch all development dependencies:

bundle

Afterwards start the test runner:

rake spec

If something goes wrong you should be noticed through failing examples.

Development

Bug reports and feature requests

Please use the issue tracker on github.com to let me know about errors or ideas for improvement of this software.

Source code

Distribution

This software is developed in the source code management system Git. There are several synchronized mirror repositories available:

• GitHub (located in California, USA)

  URL: https://github.com/godobject/user-choices-pathname.git

• Gitorious (located in Norway)

  URL: https://git.gitorious.org/user-choices-pathname/user-choices-pathname.git

• BitBucket (located in Colorado, USA)

  URL: https://bitbucket.org/godobject/user-choices-pathname.git

• Pikacode (located in France)

  URL: https://pikacode.com/godobject/user-choices-pathname.git

You can get the latest source code with the following command, while exchanging the placeholder for one of the mirror URLs:

git clone MIRROR_URL

Tags and cryptographic verification

The final commit before each released gem version will be marked by a tag named like the version with a prefixed lower-case "v", as required by Semantic Versioning. Every tag will be signed by my OpenPGP public key which enables you to verify your copy of the code cryptographically.

Add the key to your GnuPG keyring by the following command:

gpg --import aef-openpgp.asc

This command will tell you if your code is of integrity and authentic:

git tag -v [TAG NAME]

Building gems

To package your state of the source code into a gem package use the following command:

rake build

The gem will be generated according to the .gemspec file in the project root directory and will be placed into the pkg/ directory.

Contribution

Help on making this software better is always very appreciated. If you want your changes to be included in the official release, please clone the project on github.com, create a named branch to commit, push your changes into it and send a pull request afterwards.

Please make sure to write tests for your changes so that no one else will break them when changing other things. Also notice that an inclusion of your changes cannot be guaranteed before reviewing them.

The following people were involved in development:

• Alexander E. Fischer

License

Copyright GodObject Team [email protected], 2009-2013

This file is part of Pathname for user-choices.

Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.