Re: building web-octave requires Jekyll 3.3

[siko1056]

Mike Miller-4 wrote
> [...]
> Is it possible to put a minimum version requirement in _config.yml so this
> could be caught automatically and prevent someone from building and
> pushing a bad build?
> [...]
> Any ideas on how to make this easier and less error-prone would be welcome
> I think.

The _config.yml does unfortunately not provide such a feature. There is
another mechanism called `Gemfile` where dependencies are checked, but I
don't find the output very informative (in my example, when I require Jekyll
v3.1.0):

$ jekyll serve
/usr/lib64/ruby/gems/2.2.0/gems/bundler-1.13.6/lib/bundler/resolver.rb:366:in
`block in verify_gemfile_dependencies_are_found!': Could not find gem
'jekyll (~> 3.1.0)' in any of the gem sources listed in your Gemfile or
available on this machine. (Bundler::GemNotFound)
        from
/usr/lib64/ruby/gems/2.2.0/gems/bundler-1.13.6/lib/bundler/resolver.rb:341:in
`each'
        from
/usr/lib64/ruby/gems/2.2.0/gems/bundler-1.13.6/lib/bundler/resolver.rb:341:in
`verify_gemfile_dependencies_are_found!'
        from
/usr/lib64/ruby/gems/2.2.0/gems/bundler-1.13.6/lib/bundler/resolver.rb:199:in
`start'
        from
/usr/lib64/ruby/gems/2.2.0/gems/bundler-1.13.6/lib/bundler/resolver.rb:181:in
`resolve'
        from
/usr/lib64/ruby/gems/2.2.0/gems/bundler-1.13.6/lib/bundler/definition.rb:250:in
`resolve'
        from
/usr/lib64/ruby/gems/2.2.0/gems/bundler-1.13.6/lib/bundler/definition.rb:174:in
`specs'
        from
/usr/lib64/ruby/gems/2.2.0/gems/bundler-1.13.6/lib/bundler/definition.rb:233:in
`specs_for'
        from
/usr/lib64/ruby/gems/2.2.0/gems/bundler-1.13.6/lib/bundler/definition.rb:222:in
`requested_specs'
        from
/usr/lib64/ruby/gems/2.2.0/gems/bundler-1.13.6/lib/bundler/runtime.rb:118:in
`block in definition_method'
        from
/usr/lib64/ruby/gems/2.2.0/gems/bundler-1.13.6/lib/bundler/runtime.rb:19:in
`setup'
        from /usr/lib64/ruby/gems/2.2.0/gems/bundler-1.13.6/lib/bundler.rb:99:in
`setup'
        from
/usr/lib64/ruby/gems/2.2.0/gems/jekyll-3.3.1/lib/jekyll/plugin_manager.rb:36:in
`require_from_bundler'
        from /usr/lib64/ruby/gems/2.2.0/gems/jekyll-3.3.1/exe/jekyll:9:in `<top
(required)>'
        from /usr/bin/jekyll:23:in `load'
        from /usr/bin/jekyll:23:in `<main>'

And before introducing more stuff like that, are we going back to use the
existing Makefile and I update the documentation accordingly? In the same
action I would move all documentation about the deployment into that
Makefike, such that the Readme.md contains only something like

make serve-local
make deploy

and is less verbose.


Mike Miller-4 wrote
> I still noticed some slight differences in the output due to the user's
> local time zone. I added "timezone" to the configuration so it should be
> consistent from now on
> 
>   http://hg.octave.org/web-octave/rev/666ca704a210
> 
> and updated the site.

Thank you for this. When working together with people from around the globe
it is certainly a better idea.

Kai.



--
View this message in context: 
http://octave.1599824.n4.nabble.com/building-web-octave-requires-Jekyll-3-3-tp4680933p4680948.html
Sent from the Octave - Maintainers mailing list archive at Nabble.com.