Am Montag, den 27.04.2020, 08:57 -0300 schrieb Antonio Terceiro: > On Sat, Apr 25, 2020 at 06:11:08PM +0200, Daniel Leidert wrote: > > Am Samstag, den 25.04.2020, 16:20 +0200 schrieb deivid: > > > > [..] > > > > I believe this is not about the number of gems in the block. When you > > > > create a jekyll application, jekyll runs `bundle install` for you, so > > > > the other gem is already included in the `Gemfile.lock` file, that's > > > > why you don't get the issue "initially". But it has nothing to do with > > > > the number of gems, but with the information you have currently > > > > included in the `Gemfile.lock` file. You can reproduce the error with > > > > a single gem by removing `gdm` from the `Gemfile`, running `bundle > > > > install`, adding it back, and then running `jekyll b` again. > > > > Confirmed. You are right here. > > FWIW, rails also runs bundler for you when you create a new app (`rails > new`). The Debian packages contains a patch to run `bundle install > --local` instead, which will just check dependencies, but not install > anything at all. > > Maybe you want to patch jekyll in a similar way. I have patched the Gemfile and the patch also got accepted upstream. Further fedora has a patch to patch out bundler (I just cc-ed you in this information). I'm just waiting for your opinion on this matter/patch. -- Regards, Daniel Leidert <dleidert@debian.org> | https://www.wgdd.de/ GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78 If you like my work consider sponsoring me via https://www.patreon.com/join/dleidert
Attachment:
signature.asc
Description: This is a digitally signed message part