ctm/aws — comment on commit 112721cc540d7b6057901599577c15299414deb5
File:  line 0
By ctm:

Sorry for not responding earlier. I didn't see your note until just now.

The problem with the original way is we were getting complaints about constants being redeclared. I tracked the problem down to the implementation of require_relative. It's been a while, but I believe the trouble was that some code was pulling in files via require_relative and some via require. require uses the load path ($:) to construct the path name. When require_relative doesn't use the load path, it generates a path that is logically the same as the one that uses the load path, but is a different string, so require pulls the file in a second time. In addition to this being unnecessary, if there are constants, we get complaints.

Here are some duplicate constant complaints I get without the above fix:

```ruby

/Users/ctm/.rvm/gems/ree-1.8.7-2010.02@indexer-bundler/gems/aws-2.5.6/lib/ses/../awsbase/utils.rb:105: warning: already initialized constant HEX
/Users/ctm/.rvm/gems/ree-1.8.7-2010.02@indexer-bundler/gems/aws-2.5.6/lib/ses/../awsbase/utils.rb:107: warning: already initialized constant TO_REMEMBER
/Users/ctm/.rvm/gems/ree-1.8.7-2010.02@indexer-bundler/gems/aws-2.5.6/lib/ses/../awsbase/utils.rb:108: warning: already initialized constant ASCII
```