anatol/quarry

Port Quarry to work with official Arch repositories

Opened this issue · 1 comments

anatol commented

Quarry project reaches 4 year soon. For all this time it shown great result in keeping ruby repository up-to-date. Current stats is: repository contains 1096 gems with update rate ~40-50 packages per week. Quarry works really well and requires little time for maintenance.

It would be really great to get quarry to maintain packages in [community] Arch repository as well. It will help to save maintainers time. It also could help to bring a lot more popular ruby packages to [community]: jekyll, vagrant, rails, ...

eli-schwartz commented

Some thoughts on this:

  • Generally, we tend to like using separate build() and package() functions, especially when compiling native code. Currently quarry PKGBUILDs do not do this. Using them outside of quarry/clean chroot builds, would result in recompiling everything every time you use e.g. makepkg --repackage, despite that that is intended to copy over built artifacts into a *.pkg.tar.xz tarball... compare to make && make DESTDIR="${pkgdir}" install or python setup.py build && python setup.py install --root="${pkgdir}"

  • The ruby packaging ecosystem for Arch Linux is way behind on running check() functions with upstream testsuites. I believe many ruby packages should have functional testsuites which can be run with rake. So quarry should detect these and run them, I guess. (This may require the previous point too. :D)