Contents

CURRENT
============================================================================
- make it debian compatible (most of which is common sense anyway)
  http://pkg-ruby-extras.alioth.debian.org/upstream-devs.html
  ✓ Distribute your software as a source code archive
    github allows that

  - Use setup.rb
    http://github.com/proutils/setup

  ✓ Remove all references to rubygems in the software you ship
  ✓ Don’t make your Rakefile depend on RubyGems

  - Make your tests and examples usable outside of your directory tree
    this might be achieved by using setup.rb anyway...

  ✓ Use a shebang that works everywhere
  ✓ Provide man pages for your binaries
  ✓ If possible, maintain a backward-compatible API


UP NEXT
============================================================================
- Improve CLI-Code
  - rescue OptionParser::InvalidOption with help screen
  - add option '-c, --config PATH - Configuration Path (default is ~/.to_pass)'
  - add ability to execute commands
  - add command to generate configuration path
  - add command to output available converters
  - add command to output available algorithms
  - handle CLI with Thor
- have some RELEASE-NOTES or CHANGELOG
  - GemSpec#post_install_message = filename


SOMEDAY
============================================================================
- test on windows
- move decision wether a string is a word or not into algorithm definition.
- add task to validate user supplied algorithms and converters
- ?? replace Rake with Thor

Version data entries

1 entries across 1 versions & 1 rubygems

Version	Path
to_pass-0.5.2	TODO