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

any chance of a homebrew formula? #28

Open
rhaynes74 opened this issue Jun 8, 2021 · 12 comments
Open

any chance of a homebrew formula? #28

rhaynes74 opened this issue Jun 8, 2021 · 12 comments

Comments

@rhaynes74
Copy link

Good day - I am interested in trying out your tool, for some reason I am getting errors during the install with various ruby packages. Any chance of putting together a homebrew package?

@phillmv
Copy link
Owner

phillmv commented Jun 8, 2021

Good day - I am interested in trying out your tool, for some reason I am getting errors during the install with various ruby packages. Any chance of putting together a homebrew package?

I would like to avoid the extra work since I don't think that's how I'll end up distributing it in the future, but I am happy to give you a hand! The app as it is is not yet friendly to outsiders, and there's likely a few broken bits. I went ahead and added some more information in the README: https://github.com/phillmv/arquivo/blob/master/README.md

If you're on homebrew, the Ruby packages at least should be relatively easy.

Would you care to share your ruby version, osx version, and any errors you've been experiencing :)?

@rhaynes74
Copy link
Author

rhaynes74 commented Jun 8, 2021 via email

@phillmv
Copy link
Owner

phillmv commented Jun 8, 2021

Looks like Apple changed some libraries around.

According to that link, can you try running:

gem install puma:4.3.5 -- --with-cflags="-Wno-error=implicit-function-declaration"

This should get the local C extension built, and then you can run bundle install again.

If that doesn't work, I can try upgrading the gem to version 5 😄.

@rhaynes74
Copy link
Author

rhaynes74 commented Jun 8, 2021 via email

@phillmv
Copy link
Owner

phillmv commented Jun 8, 2021

Hrm, looks like it's trying to re-compile Puma, which is annoying - it should have picked up the version you just compiled. What if you pass the config directly to bundler, i.e.

bundle config build.puma --with-cflags="-Wno-error=implicit-function-declaration"

and try again?

If that fails I can try upgrading Puma.

@rhaynes74
Copy link
Author

rhaynes74 commented Jun 8, 2021 via email

@phillmv
Copy link
Owner

phillmv commented Jun 8, 2021

That's bizarre! That smells like something funny going on in your build environment.

FWIW, I've never been able to get fsevents to work properly either. What happens if you tell webpacker to ignore the integrity?

To disable this check, please change check_yarn_integrity
to false in your webpacker config file (config/webpacker.yml).

i.e. edit the config/webpacker.yml file and change the check_yarn_integrity key to false.


Sorry you're experiencing this pain; this is all very valuable feedback - I need to update some gems, figure out why node is such a pain, and maybe just ship a docker image for development. I myself came across the integrity error last night for the first time.

@rhaynes74
Copy link
Author

rhaynes74 commented Jun 8, 2021 via email

@phillmv
Copy link
Owner

phillmv commented Jun 8, 2021

That's because I used an ancient version of bundler 😅, tho strange if bundle exec rails db:setup / bundle install worked; it should've given you this error then too!

Try gem install bundler:1.17.2 and see how that goes. I believe bundler can co-exist with multiple versions of itself.

@rhaynes74
Copy link
Author

rhaynes74 commented Jun 8, 2021 via email

@phillmv
Copy link
Owner

phillmv commented Jun 8, 2021

hah, cheers Ronald, thanks for getting this far. I do not at the moment, because 90% of the work I use it for can't be shown publicly, and it remains an experimental tool.

You can get a sense of some of its capabilities via this static site export: https://phillmv.github.io/public/ which generates about 70% of the functionality (i.e. no full text search, no todo lists).

If you'd like, I can ping you whenever I get around to making a hosted version.

If you don't mind me asking, how did you come across this in the first place?

Cheers,

@rhaynes74
Copy link
Author

rhaynes74 commented Jun 8, 2021 via email

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