Package Details: rubyripper 0.8.0rc3-6

Git Clone URL: https://aur.archlinux.org/rubyripper.git (read-only, click to copy)
Package Base: rubyripper
Description: Secure audiodisc ripper
Upstream URL: https://github.com/bleskodev/rubyripper
Keywords: cd ripping
Licenses: GPL-3.0-only
Submitter: xyproto
Maintainer: FabioLolix
Last Packager: FabioLolix
Votes: 13
Popularity: 0.000000
First Submitted: 2017-07-19 13:22 (UTC)
Last Updated: 2024-10-20 14:22 (UTC)

Dependencies (20)

Required by (0)

Sources (1)

Pinned Comments

FabioLolix commented on 2024-10-19 12:37 (UTC)

After every major ruby update all AUR ruby pkgbuilds need to be rebuilded

Latest Comments

« First ‹ Previous 1 2 3 4 5

Warepire commented on 2018-04-12 18:20 (UTC)

My PKGBUILD for building 0.7.0rc1 from blaskodev's github: https://github.com/Warepire/aur-rubyripper

Also had to do some minor fixes. For me this one is less crash prone than 0.6.2.

ElektroQuark commented on 2018-01-05 08:13 (UTC)

It looks like the bleskodev fork is maintained (some bugs patched time to time). I would like to change this package to use the git version from bleskodev, just in case ;)

Thank you.

QuimaxW commented on 2017-11-05 12:16 (UTC)

@s0nspark, did you notice any improvements over the old setup?

s0nspark commented on 2017-11-03 00:14 (UTC)

I built a local package using this PKGBUILD as a guide. The only changes I made were to pull the updated blescodev code from github and add a tiny patch to remove a deprecation warning regarding GdkPixbuf. I chose to build against local gems instead of the ruby-iconv, ruby-gettext and ruby-gtk2 packages since I use rbenv for all of my ruby needs but everything seems to work well. It is rare I have to rip a CD these days but I like using this tool when the need arises :-)

QuimaxW commented on 2017-09-21 09:43 (UTC)

I adopted this mostly to ensure it doesn't disappear! Having no idea who may still follow this package, has anyone any experience building bleskodev's fork from https://github.com/bleskodev/rubyripper ? I'm thinking of copying this package, then modifying it to use the fork, just to see if it works. Or perhaps it would be easier to simply update this package? Thoughts?

« First ‹ Previous 1 2 3 4 5