Re: building web-octave requires Jekyll 3.3

[Mike Miller]

On Thu, Dec 08, 2016 at 08:09:06 -0800, siko1056 wrote:
> 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):

Yes, I locally used a Gemfile and bundler to install all of the
necessary gems into a vendor directory (what I understand to be a
typical ruby project setup). I'm not sure if we want to go full ruby
with this repo or what the right solution is.

> 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.

That looks good.

Maybe we could have the makefile error out if jekyll --version is less
than 3.3? Are there other critical dependencies? I also had some odd
markup differences in code blocks, maybe due to a different version of
kramdown.

-- 
mike