gemfile_lock_to_gemfile 0.1.0 → 0.1.1
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/gemfile_lock_to_gemfile.gemspec +29 -0
- metadata +2 -1
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA1:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 4d704d4f8674075e3814414fa572f67ef9c3da31
|
|
4
|
+
data.tar.gz: 53edc49061c2028d6879205ccebf09335b3ad530
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 4281434088d164eb493ae1017d913295cc3dd3faa68efead9a13cff7119e53faf24211a51f37b5c3997108584da0ae4d3e8a2889a32b912ccb399869d5f58374
|
|
7
|
+
data.tar.gz: 5bb625b6506c896dfe052030cdd1d0756ab8ebe7c727d47bd2e2b9dac56a43bebfd51c2587a72ae6b6ed64dbc96ac8aad6600550077a9728914595a20bd6081b
|
|
@@ -0,0 +1,29 @@
|
|
|
1
|
+
# frozen_string_literal: true
|
|
2
|
+
|
|
3
|
+
Gem::Specification.new do |s|
|
|
4
|
+
s.name = "gemfile_lock_to_gemfile"
|
|
5
|
+
s.version = "0.1.1"
|
|
6
|
+
s.date = Time.now.strftime('%Y-%m-%d')
|
|
7
|
+
s.summary = "A tool for reversing `Gemfile.lock` -> `Gemfile`"
|
|
8
|
+
s.homepage = "https://github.com/agate/gemfile_lock_to_gemfile"
|
|
9
|
+
s.email = "agate.hao@gmail.com"
|
|
10
|
+
s.authors = [ "agate" ]
|
|
11
|
+
s.has_rdoc = false
|
|
12
|
+
|
|
13
|
+
s.files = %w( README.md Rakefile LICENSE gemfile_lock_to_gemfile.gemspec )
|
|
14
|
+
s.files += Dir.glob("lib/**/*")
|
|
15
|
+
s.files += Dir.glob("bin/**/*")
|
|
16
|
+
s.files += Dir.glob("man/**/*")
|
|
17
|
+
s.files += Dir.glob("test/**/*")
|
|
18
|
+
|
|
19
|
+
s.executables = %w( gemfile_lock_to_gemfile )
|
|
20
|
+
s.description = <<END
|
|
21
|
+
## Why I have to develop this tool
|
|
22
|
+
|
|
23
|
+
One of my ruby project is using bundler to manage gem dependencies. But the `Gemfile` is very complicate. It requires external `Gemfile` by using ruby `eval`. Because I have lots of similar projects that will use same piece of gems. So I decide to abstract these gems into a standalone `Gemfile`. And let those projects’ `Gemfile` loads it.
|
|
24
|
+
|
|
25
|
+
The problem I met is when I building my docker image. I hope that image can pre-install all the ruby gems in that `Gemfile.lock`. Unluckily, `bundle install` require you must have the `Gemfile`. So I have to find out a way to revert `Gemfile.lock` to a usable `Gemfile`.
|
|
26
|
+
|
|
27
|
+
So here we are!
|
|
28
|
+
END
|
|
29
|
+
end
|
metadata
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: gemfile_lock_to_gemfile
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.1.
|
|
4
|
+
version: 0.1.1
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- agate
|
|
@@ -28,6 +28,7 @@ files:
|
|
|
28
28
|
- README.md
|
|
29
29
|
- Rakefile
|
|
30
30
|
- bin/gemfile_lock_to_gemfile
|
|
31
|
+
- gemfile_lock_to_gemfile.gemspec
|
|
31
32
|
- lib/gemfile_lock_to_gemfile.rb
|
|
32
33
|
- lib/gemfile_lock_to_gemfile/converter.rb
|
|
33
34
|
- test/resources/Gemfile
|