summaryrefslogtreecommitdiff
path: root/.gemspec
AgeCommit message (Collapse)Author
2013-04-12Update gemspec, Modulefile, CHANGELOG for 4.0.2Jeff McCune
Without this patch the information displayed on rubygems.org does not clearly convey the intent of the Gem format of stdlib from the official puppet module format of stdlib. This is a problem because end users might get confused and start installing stdlib from rubygems.org This patch addresses the problem by making it clear that the gem version of stdlib is not intended for end users, but rather is specifically intended to make it easier for other module authors to depend on stdlib and have that dependency automatically resolved using a Gemfile. [ci skip]
2013-04-11Update gemspec, CHANGELOG, Modulefile for 4.0.1Jeff McCune
2013-04-11Update gemspec for 4.0.0Jeff McCune
2013-04-10(maint) Make stdlib usable as a Ruby GEMJeff McCune
Without this patch it is inconvenient to use the functions included in stdlib in a development setting. The Puppet modulepath must be explicitly set for the functions to be automatically loaded. This patch addresses the problem by adding a gem specification and dependency Gemfile. This makes it possible to directly use stdlib and all of the components it depends upon, like so: $ bundle install --path .bundle/gems/ $ bundle exec puppet apply -e 'notice count([1, 2, 3])' The first command will install all of the dependencies, including Puppet and Facter, into the local project directory. The second command will make stdlib avaialable as a Gem, which will be picked up by Puppet since (#7788) was merged into Puppet in the 3.0 release.