Package Details: ruby-liquid 5.5.0-1

Git Clone URL: (read-only, click to copy)
Package Base: ruby-liquid
Description: Liquid markup language. Safe, customer facing template language for flexible web apps
Upstream URL:
Keywords: ruby
Licenses: MIT
Submitter: patrick.luehne
Maintainer: patrick.luehne (bertptrs)
Last Packager: bertptrs
Votes: 10
Popularity: 0.000090
First Submitted: 2017-10-10 22:25 (UTC)
Last Updated: 2024-03-21 21:30 (UTC)

Dependencies (2)

Required by (2)

Sources (1)

Latest Comments

patrick.luehne commented on 2018-08-23 17:03 (UTC)

@alex.shpilkin, J5lx: Sorry for the wait. I finally updated the PKGBUILD with the missing build dependency and pushed a new package release :). Thanks to both of your for pointing out the missing make dependency!

J5lx commented on 2018-08-02 13:40 (UTC)

As mentioned by alex.shpilkin, this package needs ruby-rdoc in order to build, please add it to the dependencies!

alex.shpilkin commented on 2018-07-13 07:03 (UTC)

@patrick.luehne The current ruby package no longer includes rdoc, so this package needs to have a makedepend on ruby-rdoc or it won’t build.

patrick.luehne commented on 2017-11-20 17:37 (UTC)

@bertptrs: Thanks for your fix and explanation :)! I fixed the PKGBUILD and incremented the pkgrel to fix this for other users who might not have noticed this issue yet. I’m sorry to hear that this PKGBUILD apparently caused you trouble when installing this package! I based this PKGBUILD on the Ruby packages in the Arch community repository, such as ruby-celluloid or ruby-addressable, which commonly use the approach of “$(gem env gemdir)”. However, I assume that this less of an issue for the Arch packagers, because they use clean machines for packaging. I also fixed the PKGBUILD of my other Ruby package, ruby-ruby_dep.

bertptrs commented on 2017-11-20 11:04 (UTC)

Due to a mistake in the PKGBUILD, this package installed its gem files into my homedir. Instead of detecting the gemdir like "$(gem env gemdir)", which gives the user gemdir, you can detect it like this "$(ruby -e'puts Gem.default_dir')" which other packages use. This issue is caused by a setup as described in, which I suspect will be common among Arch users.

SilverRainZ commented on 2017-11-20 05:02 (UTC)

@patrick.luehne, My fault, yes the pkgname is already automaticly added into `provides`. ref:

patrick.luehne commented on 2017-10-17 14:09 (UTC)

@SilverRainz: Many thanks for your suggestion! I think it would be a good idea to resolve the situation with the multiple existing ruby-liquid packages. However, isn’t your “provides” directive implicit, as this package is already called “ruby-liquid”? (If I’m wrong, I would be happy if you could point me to a reference.) Also, it seems to me that “provides” directives may not contain comparison operators except ‘=’.

SilverRainZ commented on 2017-10-16 10:36 (UTC)

I think it will be better to add `provides = ('ruby-liquid>=4.0')` into PKGBUILD.

patrick.luehne commented on 2017-10-10 22:28 (UTC)

This package is meant to make Jekyll work, which requires Liquid 4.0.0 as of Jekyll 3.6.0, and there was no Liquid package recent enough. This is just a temporary solution before Liquid is made available through Arch’s official community packages. I’m aware of the fact that there are ruby-liquid-2.0 and ruby-liquid-3 packages, but I think the most current version should be in a package without any version number in the package name (and the older ones should only exist if still required by some other package). This is why I named this package ruby-liquid and not ruby-liquid-4.