On Thursday, 28 October 2021 13:34:49 BST Alec Ten Harmsel wrote: > I got jekyll installed via portage by adding: > > dev-ruby/* ~amd64 > www-apps/jekyll ~amd64 > www-apps/jekyll-* ~amd64 > > to package.accept_keywords, and then running `emerge www-apps/jekyll'. > This is on stable, with a tree that is a couple weeks old for what it's > worth.
This system is ~amd64, so I didn't have to do that. > Then `jekyll new testsite && bundle exec jekyll serve' works for me. $ jekyll new myblog && bundle exec jekyll serve ... [A number of Bundler: Using... messages] ... New jekyll site installed in /home/prh/myblog. Could not locate Gemfile or .bundle/ directory # find / -xdev -iname gemfile /usr/lib64/ruby/gems/3.0.0/gems/jekyll-seo-tag-2.7.1/Gemfile /usr/lib64/ruby/gems/3.0.0/gems/bundler-2.2.29/lib/bundler/templates/Gemfile /usr/lib64/ruby/gems/2.6.0/gems/bundler-2.2.29/lib/bundler/templates/Gemfile /usr/lib64/ruby/gems/2.6.0/gems/jekyll-4.2.0/lib/theme_template/Gemfile $ find . -xdev -iname gemfile ./.local/share/gem/ruby/3.0.0/gems/jekyll-4.2.1/lib/theme_template/Gemfile ./.local/share/gem/ruby/3.0.0/gems/mercenary-0.4.0/Gemfile ./.local/share/gem/ruby/3.0.0/gems/terminal-table-2.0.0/Gemfile ./.local/share/gem/ruby/3.0.0/gems/http_parser.rb-0.6.0/Gemfile ./.local/share/gem/ruby/3.0.0/gems/bundler-2.2.30/lib/bundler/templates/Gemfile ./.local/share/gem/ruby/3.0.0/gems/addressable-2.8.0/Gemfile ./.local/share/gem/ruby/3.0.0/gems/forwardable-extended-2.6.0/Gemfile ./.local/share/gem/ruby/3.0.0/gems/rb-inotify-0.10.1/Gemfile ./.local/share/gem/ruby/3.0.0/gems/em-websocket-0.5.2/Gemfile ./.local/share/gem/ruby/3.0.0/gems/sassc-2.4.0/Gemfile ./.local/share/gem/ruby/3.0.0/gems/concurrent-ruby-1.1.9/Gemfile ./.local/share/gem/ruby/3.0.0/gems/safe_yaml-1.0.5/Gemfile ./.local/share/gem/ruby/3.0.0/gems/rb-fsevent-0.11.0/Gemfile ./.local/share/gem/ruby/3.0.0/gems/bundler-2.2.29/lib/bundler/templates/Gemfile ./.local/share/gem/ruby/3.0.0/gems/ffi-1.15.4/Gemfile ./.local/share/gem/ruby/3.0.0/gems/colorator-1.1.0/Gemfile ./.local/share/gem/ruby/3.0.0/gems/rouge-3.26.1/Gemfile ./.local/share/gem/ruby/3.0.0/gems/public_suffix-4.0.6/Gemfile ./.local/share/gem/ruby/3.0.0/gems/pathutil-0.16.2/Gemfile ./myblog/Gemfile $ grep -v \# myblog/Gemfile | grep -v ^$ source "https://rubygems.org"; gem "jekyll", "~> 4.2.0" gem "minima", "~> 2.5" group :jekyll_plugins do gem "jekyll-feed", "~> 0.12" end platforms :mingw, :x64_mingw, :mswin, :jruby do gem "tzinfo", "~> 1.2" gem "tzinfo-data" end gem "wdm", "~> 0.1.1", :platforms => [:mingw, :x64_mingw, :mswin] (That last line relates to Windows and Jruby.) It still looks like a PATH problem, but what do I know? :( > You could also try using jekyll outside of portage: > > mkdir mysite && cd mysite > bundle init > bundle config set path 'vendor/bundle' > bundle add jekyll > bundle exec jekyll new --force . > rm Gemfile.lock > rm -rf ./vendor/bundle > bundle config set path 'vendor/bundle' > bundle install > bundle exec jekyll serve > > And then continue following other jekyll instructions as needed. You'll have > to use `bundle exec jekyll ...' to run jekyll - you won't be able to run > jekyll directly. Thanks Alec. I may have to try something like that, but I'd rather have it installed by portage if I can. Perhaps I'm just growing too old for this sort of thing... -- Regards, Peter.
