Package Details: jekyll 3.8.5-2

Git Clone URL: (read-only)
Package Base: jekyll
Description: A simple, blog aware, static site generator.
Upstream URL:
Keywords: jekyll ruby
Licenses: MIT
Conflicts: ruby-jekyll
Provides: jekyll=3.8.5, ruby-jekyll
Replaces: ruby-jekyll
Submitter: SilverRainZ
Maintainer: SilverRainZ (bjo)
Last Packager: bjo
Votes: 72
Popularity: 0.920263
First Submitted: 2017-11-20 05:56
Last Updated: 2019-01-21 16:03

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 ... Next › Last »

mschu commented on 2015-08-17 23:13

celluloid needs to be version 16 as well:

sorry for spamming you so much, let me know if you need help fixing the deps :-)

mschu commented on 2015-08-17 23:05

And further celluloid, rspec-logsplit, hitimes, timers, celluloid-extras, celluloid-fsm, celluloid-pool, celluloid-supervision, celluloid-essentials, bundler, nenv, dotenv, rb-fsevent, ffi, rb-inotify.

And community/nodejs or another JS framework as ItachiSan pointed out.

mschu commented on 2015-08-17 22:51

I still get an error message when running Jekyll in my page directory:

/usr/lib/ruby/2.2.0/rubygems/dependency.rb:315:in `to_specs': Could not find 'jekyll-sass-converter' (~> 1.0) among 30 total gem(s) (Gem::LoadError)

Seems to need a depends on ruby-jekyll-sass-converter. And ruby-jekyll-watch, which is missing ruby-listen (there is already a comment on the package).

WhyNotHugo commented on 2015-08-14 02:20

Just pushed ruby-kramdown. Thanks for the heads up.

mschu commented on 2015-08-09 22:00

This is missing at least the ruby-kramdown dependency in AUR4.

ItachiSan commented on 2015-07-24 15:14

And also a JavaScript environment, else Jekyll won't run. Actually, 'nodejs' from community works fine.

ItachiSan commented on 2015-07-24 15:04

You should add 'ruby-jekyll-sass-converter' as a dependency.

kralyk commented on 2015-05-19 01:18

@anatolik Thanks, that's great!

WhyNotHugo commented on 2015-05-16 20:20

(or viceversa)

WhyNotHugo commented on 2015-05-16 20:20

I admit that current packaging is awful. I'm willing to merge all this into a single package, *however*, is there any valid scenario under which someone would use ruby-jekyll-less, without ruby-jekyll?