Permalink
Browse files

Cache vendored gems

  • Loading branch information...
rodjek committed May 25, 2012
1 parent 1b1d558 commit 1a6ad365694fc1e608a0a04ea35c292d00e2b6f2
View
@@ -0,0 +1,2 @@
+.bundle/
+vendor/gems
View
@@ -0,0 +1,28 @@
+GEM
+ remote: http://rubygems.org/
+ specs:
+ diff-lcs (1.1.3)
+ facter (1.6.9)
+ puppet (2.7.14)
+ facter (>= 1.5.1)
+ puppet-lint (0.1.13)
+ rake (0.9.2.2)
+ rspec (2.10.0)
+ rspec-core (~> 2.10.0)
+ rspec-expectations (~> 2.10.0)
+ rspec-mocks (~> 2.10.0)
+ rspec-core (2.10.1)
+ rspec-expectations (2.10.0)
+ diff-lcs (~> 1.1.3)
+ rspec-mocks (2.10.1)
+ rspec-puppet (0.1.3)
+ rspec
+
+PLATFORMS
+ ruby
+
+DEPENDENCIES
+ puppet (>= 2.7)
+ puppet-lint
+ rake
+ rspec-puppet
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.

2 comments on commit 1a6ad36

@malthe

This comment has been minimized.

Show comment Hide comment
@malthe

malthe Mar 18, 2014

Why would you include binary gems in your repository? Did you even check the licenses?

Your module is supposed to make it "easy" to write logrotate.d rules such as:

/var/log/dpkg.log {
    monthly
    rotate 12
}

I'm not sure it can be justified to generate such a rule in the first place, but certainly using 3.2 megabytes to pull off that stunt is rather gross.

tcp90

Why would you include binary gems in your repository? Did you even check the licenses?

Your module is supposed to make it "easy" to write logrotate.d rules such as:

/var/log/dpkg.log {
    monthly
    rotate 12
}

I'm not sure it can be justified to generate such a rule in the first place, but certainly using 3.2 megabytes to pull off that stunt is rather gross.

tcp90

@rodjek

This comment has been minimized.

Show comment Hide comment
@rodjek

rodjek Mar 18, 2014

Owner

Why would you include binary gems in your repository?

  • Because rubygems.org doesn't have the greatest uptime.
  • Because I like to work in places that don't have internet connectivity (like planes).
  • Because it's my repo and I'll do as I damn well please

Pick one.

Did you even check the licenses?

You mean the MIT and Apache licenses that allow redistribution?

I'm not sure it can be justified to generate such a rule in the first place

So don't use my module, I'm sure as hell not going to force you.

using 3.2 megabytes

Perhaps use the packages built for distribution that are 12Kb in size instead of my development environment?

rather gross

Owner

rodjek replied Mar 18, 2014

Why would you include binary gems in your repository?

  • Because rubygems.org doesn't have the greatest uptime.
  • Because I like to work in places that don't have internet connectivity (like planes).
  • Because it's my repo and I'll do as I damn well please

Pick one.

Did you even check the licenses?

You mean the MIT and Apache licenses that allow redistribution?

I'm not sure it can be justified to generate such a rule in the first place

So don't use my module, I'm sure as hell not going to force you.

using 3.2 megabytes

Perhaps use the packages built for distribution that are 12Kb in size instead of my development environment?

rather gross

Please sign in to comment.