Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Port Quarry to work with official Arch repositories #84

Open
anatol opened this issue Feb 15, 2018 · 1 comment
Open

Port Quarry to work with official Arch repositories #84

anatol opened this issue Feb 15, 2018 · 1 comment

Comments

@anatol
Copy link
Owner

anatol commented Feb 15, 2018

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
Copy link
Contributor

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants