[DRE-maint] Bug#942596: Bug#942596: jekyll and required bundles

[ydirson at 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 stable-backports. If you are missing some please let me
> know. Just
> add the plugins you need to Gemfile and _config.yml, run jekyll, and
> that
> should be it. In case of a missing theme (I just packaged the minima
> theme) one
> can use the ruby-jekyll-remote-theme package (and the plugin inside)
> to avoid
> bundler.

That one works fine indeed, both with ruby 2.5 and 2.7 (2.7 issues
language warnings that were apparently handled in 4.0.0, but they're
just warnings).

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.

I don't really see a nice route with this for packaging: just documenting
the fact and add a user notice in "jekyll new" that the package won't work
until the file is removed feels awkward.

OTOH, doesn't it feel awkward as well that just having Gemfile present
causes the system binary to do what looks like a "bundle exec" ?   Again
I'm too noob with ruby to say for sure, but that sure confused me.

Best regards,
-- 
Yann