gistfile1

0 days) The package is available and an automated install is patterned.
1 days) The OS (distribution) provides a package that provides the functionality
         and the automation pattern needs designed/written
2 days) There is a external source that provides a package that provides the 
         functionality (epel,dag,debian-backports) and the automation needs 
         designed
4 days) The source tarball is easily (w/a re-useable script) converted into a 
         package (cpanflute2/mkdeb/dh-make-perl), automation pattern design 
         needed
8 days) Something needs to be custom-scripted to build the package, and automate
         the configuration to add the functionality
16 days) Something needs to be custom written and packaged to provide the 
          functionality and automate the install
32 days) A manual process needs to be wrapped around something because it can't
          be automated


* add 1 day for each item so that a way to monitor them can be patterned.
** On Microsoft Windows, all time values are doubled and there is usually an 
    additional software purchase of some type required.