This repository has been archived by the owner. It is now read-only.
Permalink
Browse files

Document passing --path to librarian-puppet in FAQ

If this option is omitted, librarian-puppet will install modules to its
default path, which will then clash with the ones installed by Boxen.
  • Loading branch information...
eugeneius committed Mar 24, 2016
1 parent 108e64c commit 65588e3de5e332aaa13732747e249da9136ba605
Showing with 2 additions and 2 deletions.
  1. +2 −2 docs/faq.md
View
@@ -54,7 +54,7 @@ The next step is to update your Puppet modules and RubyGems. First delete Puppet
```bash
rm Puppetfile.lock Gemfile.lock
bundle install --no-deployment --without development --path .bundle
bundle exec librarian-puppet install --clean
bundle exec librarian-puppet install --path=shared --clean
```
### Q: What's a good approach to merging our-boxen back into my private fork?
@@ -65,7 +65,7 @@ One approach is to delete the Gemfile.lock and Puppetfile.lock and run:
bundle install --without development --path .bundle
# Regenerates Puppetfile.lock and caches tarballs
bundle exec librarian-puppet install --clean
bundle exec librarian-puppet install --path=shared --clean
These will generate the respective lock files suitable for committing. Hope that helps.

0 comments on commit 65588e3

Please sign in to comment.