[DRE-maint] Bug#942596: Bug#942596: jekyll and required bundles
Daniel Leidert
dleidert at debian.org
Mon Apr 20 15:19:17 BST 2020
Am Sonntag, den 19.04.2020, 18:28 +0200 schrieb ydirson at 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"
Why? You have three choices:
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.
2) Use the package management and bundler at least partly. In this case set
GEM_HOME and GEM_PATH accordingly in your user account to install gems into
your user account (`bundle env`) and not /var or vendor/bundle. I don't
recommend this at all if you don't know what you are doing, because things can
become quite difficult and painful.
3) Use bundler completely (set GEM_HOME, GEM_PATH) and use `bundle <command> --
path vendor/bundle`. In this case you don't need any Debian package except for
ruby itself.
In option 2 and 3 you are on your own and should get support from a ruby
community. You will also need the build-essential and ruby-dev packages as well
as other -dev packages depending on the Ruby extension bundler tries to build.
[..]
> Being quite a stranger to ruby things (which is usually a good starting point
> for validating a user documentation ;),
> all this is extremely confusing :)
I understand. Please stick to the Debian packages then and remove all gems from
your system (usually vendor/bundle, ~/.bundle, Gemfile.lock, ~/.gems, etc.). We
are responsible for the Debian package management and I run jekyll perfectly
without using bundler at all:
https://salsa.debian.org/ruby-team/ruby-team.pages.debian.net
https://salsa.debian.org/debichem-team/debichem-team.pages.debian.net
If you are a stable user please let me know which of the plugins you need are
missing in backports. My goal is to provide a full jekyll environment for
current stable users (upcoming stable will have full support).
https://packages.debian.org/search?keywords=jekyll
> For a start, you could include a step-by-step instruction sheet to make use
> of jekyll in Debian.
That's a good idea. I'll add a README file to jekyll and update the jekyll
backport as soon as jekyll-theme-minima hits testing.
For now:
jekyll new --skip-bundler
Adjust Gemfile and _config.yml to contain the plugins you need (see the two
project links above). Install the plugins you need (see the packages page
above). Add your content and run `jekyll s` or `jekyll b`. See `man jekyll` for
more information (jekyll 3.8.6 is in backports too).
Regards, Daniel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-ruby-extras-maintainers/attachments/20200420/0e70802a/attachment.sig>
More information about the Pkg-ruby-extras-maintainers
mailing list