Hi Daniel,
> > I finally understood what confused me at first: even with
> > --skip-bundle,
> > "jekyll new" creates a Gemfile. And until this Gemfile is removed,
> > "jekyll build" will try to go the bundle way all by itself.
>
> That is not true. As I explained earlier I'm using jekyll myself
Am Samstag, den 25.04.2020, 00:18 +0200 schrieb ydir...@free.fr:
> Hi Daniel,
>
> - Mail original -
> > 1) Use the Debian package management and don't use bunlder at all
> > (jekyll new
> > --skip-bundle). All the Jekyll plugins have been packaged and most of
> > them can
> > be found in s
Hi Daniel,
- Mail original -
> 1) Use the Debian package management and don't use bunlder at all
> (jekyll new
> --skip-bundle). All the Jekyll plugins have been packaged and most of
> them can
> be found in stable-backports. If you are missing some please let me
> know. Just
> add the plu
Hi Daniel,
- Mail original -
> De: "Daniel Leidert"
> À: ydir...@free.fr, 942...@bugs.debian.org
> Envoyé: Lundi 20 Avril 2020 16:19:17
> Objet: Re: [DRE-maint] Bug#942596: jekyll and required bundles
>
> Am Sonntag, den 19.04.2020, 18:28 +0200 schrieb ydir...@free.fr:
> > Trying Jekyll
Am Sonntag, den 19.04.2020, 18:28 +0200 schrieb ydir...@free.fr:
> Trying Jekyll for the first time, I get hit by the same issue.
>
> Indeed this flag is a good start, but afterwards:
>
> 1. we have to gather we should change the Gemfile to use:
>
> source "file:///usr/lib/ruby/vendor_ruby"
Wh
5 matches
Mail list logo
