You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
while it is NOT under git-manaed because it is just copy of the sources (without .git/*).
This situation causes the following 'fatal' git error:
$ bundle exec rake -T
fatal: not a git repository (or any of the parent directories): .git
...
The interesting thing is that another gem without 'path' option doesn't generate such a git error. It could be because the gemspec file is not invoked (since cached?) even though the gemspec contains the same git ls-file -z.
Did you try upgrading rubygems & bundler?
no
Post steps to reproduce the problem
create 'hello' gem
$ mkdir work; cd work
$ bundle gem hello
$ cd hello
$ git init
$ vi hello.gemspec # modify 'TODO' to avoid gem error
$ git add .
$ git commit
create 'hello' sources just for testing
$ git archive -o /tmp/hello.tgz --prefix hello-gem/ HEAD
install 'hello' gem
$ cd .. # goto ~/work
$ tar zxvf /tmp/hello.tgz
create test app and refer 'hello' gem via path option
$ bundle install
$ bundle exec rake -T
fatal: not a git repository (or any of the parent directories): .git
rake hello # say hello
Which command did you run?
bundle
What were you expecting to happen?
doesn't generate git fatal error. Is there any other solution than 'path' option to install 'hello' gem without git repository? user-install option is the solution?(it cached and doesn't invoke hello.gemspec?)
What actually happened?
hello.gemspec is invoked on every 'bundle exec' execution and it generates git error:
fatal: not a git repository (or any of the parent directories): .git
The text was updated successfully, but these errors were encountered:
Describe the problem as clearly as you can
When I specify 'path' option in Gemfile as follows:
Then, the ../hello-gem/hello.gemspec is always invoked on
bundle exec ...
.When the hello-gem's hello.gemspec contains the followings (normally generated by
bundle gem
):while it is NOT under git-manaed because it is just copy of the sources (without .git/*).
This situation causes the following 'fatal' git error:
$ bundle exec rake -T fatal: not a git repository (or any of the parent directories): .git ...
The interesting thing is that another gem without 'path' option doesn't generate such a git error. It could be because the gemspec file is not invoked (since cached?) even though the gemspec contains the same
git ls-file -z
.Did you try upgrading rubygems & bundler?
no
Post steps to reproduce the problem
modify as follows
create Rakefile
as follows
Which command did you run?
bundle
What were you expecting to happen?
doesn't generate git fatal error. Is there any other solution than 'path' option to install 'hello' gem without git repository?
user-install
option is the solution?(it cached and doesn't invoke hello.gemspec?)What actually happened?
hello.gemspec is invoked on every 'bundle exec' execution and it generates git error:
The text was updated successfully, but these errors were encountered: