-
Notifications
You must be signed in to change notification settings - Fork 474
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
Better native-client updates management (homebrew, packages) #92
Comments
What about making it an official Debian package? Cf. today's post at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972429 by Barak A. Pearlmutter. |
I am working on a |
I am still working to make sure the Debian package has no security issues; #93 |
I am trying to keep the native side as simple as possible. Almost all the functionalities are handled on the extension side, even the native node script that is supposed to get executed. Currently, the only reason for updating this client is to support new extensions or occasionally update the node executable. |
I am working on a deb package for Linux. As far as I know, Homebrew cannot be used to copy files to the home directory, so it is not useful for copying metafiles to the browser-specific paths. I don't have any experience with |
I have very little experience with Debian packages, just from time to time I produce the new version of our djview4poliqarp (always with just |
Current installation instructions and process of 'native-client' install/update is cumbersome. Is there any way to update the native-client using known package management tools, e.g. 'homebrew' on mac, 'chocolatey' on win?
The text was updated successfully, but these errors were encountered: