Fixed relative paths issue
remove write instead of setting absolute permissions
remove write instead of setting absolute permissions
remove write instead of setting absolute permissions
remove write instead of setting absolute permissions
remove write instead of setting absolute permissions
remove write instead of setting absolute permissions
include path in error message
switch from glob to File::Find::Rule
fix importing a function into base_class causing result class to break

This is super weird.  Why would a parent class override a subclass?  I
hope it's safe to limit this behavior to just properties.  Importing
'mode' into Genome::SoftwareResult::Stageable broke
Genome::Model::Tools::Htseq::Count because that class has a property
named 'mode'.
remove commented out code
remove write instead of setting absolute permissions

Setting absolute permissions is often not the correct thing to do because it
doesn't account for other bits the file/directory might have, e.g. setgid, or
executable.  So, for example, instead of setting thing readonly by doing `chmod
444` one could instead do `chmod a-w`.