-
Notifications
You must be signed in to change notification settings - Fork 57
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
custom luvi #180
Comments
Actually I've been playing with this last week.
Using both these my solution is to compile custom luvi for alpine (just clone luvi source and build normally inside alpine). I put it at > lit make lit://luvit/luvit /usr/local/bin/luvit /path/to/prefix And it will build the zip for The undocumented feature is the 3rd argument to |
I would like to think of some tweaks to luvi that makes this custom luvi easier, maybe a config option? |
Thanks for the prompt response! A config option would be helpful to force a custom version of luvi instead of grabbing a prebuild binary |
Agreed, I'll leave this issue open as a reminder to add such an option when I'm back at my desk next week. |
Hello, I have run in a bit of trouble running in Alpine Linux, and musl.
Since lit will download the supposedly right version of the precompiled binary from github it will not run on my small system (an ARM server from scaleway and my Raspberry).
I already have luvi, lit and luvit installed in
/usr/local
. Additionally I had to replace the downloaded luvi with my compiled version~/.litdb.git/cache/24339028e53ad0607172d8c0f0105a5814cd7bc9/luvi
.A quick inspection of the code revealed tha there is currently no way to set a preferred
luvi
executable. Is this something you would like to support? If you are positive I could give it a try and send a pull request.Tests are all green in Alpine
3.3.3
, kernel4.3.3-std-1
platformarmv7l
The text was updated successfully, but these errors were encountered: