| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
- All previous File.unlink calls go through the new FileSystem::File
abstraction so that the implementation can later be swapped for a
Windows specific one to support symlinks
|
|
- All previous File and FileTest calls to exist? or exists? go through
the new FileSystem::File abstraction so that the implementation can
later be swapped for a Windows specific one to support symlinks
|
|
Without this patch Ruby 1.9 is still complaining loudly about trying to
parse the spec files. The previous attempt to clean up this problem in
edc3ddf works for Ruby 1.8 but not 1.9.
I'd prefer to remove the shebang lines entirely, but doing so will cause
encoding errors in Ruby 1.9. This patch strives for a happy middle
ground of convincing Ruby it is actually working with Ruby while not
confusing it to think it should exec() to rspec.
This patch is the result of the following command run against the source
tree:
find spec -type f -print0 | \
xargs -0 perl -pl -i -e 's,^\#\!\s?/(.*)rspec,\#! /usr/bin/env ruby,'
|
|
For a bunch of local caching and retrieval, Puppet uses a YAML backed local
file terminus to store, retrieve, and search content. This is great, but the
YAML encoder is super-slow and painfully odd across Ruby versions.
Our PSON support is much more reliable, as well as substantially faster, and
is pretty much as capable. There isn't much reason, other than migration
cost, to prefer YAML to PSON encoding of data transfer documents.
Having a JSON terminus allows the user to configure, manually, the use of JSON
everywhere that we previously used YAML. While this doesn't bring the
benefits out of the box, it allows users to select this while we flush out any
lingering bugs left in the support code and system.
Signed-off-by: Daniel Pittman <daniel@puppetlabs.com>
|
