Binary files should not be in /usr/share/
See original GitHub issueWhat version of electron-installer-debian
are you using?
0.3.1
What version of node
and npm
are you using?
v6.1.0
3.8.6
What operating system are you using?
debian jessie
What did you do? Please include the configuration you are using for electron-installer-debian
.
Built a debian package from an electron package. No special configuration.
electron-installer-debian --src etcher-release/Etcher-linux-x64/ --dest etcher-release/debian/ --arch amd64
What did you expect to happen?
In the package that was created, /usr/share/
should only contain architecture interdependent files.
What actually happened?
/usr/share/
contains architecture dependent binary files.
Installing the electron package to /usr/lib/<package>
instead of /usr/share/<package>
would be more appropriate.
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Why is it best practice to ignore binary files? - Stack Overflow
Binary files are usually not written directly by a human being, they tend to be generated from some kind of a source.
Read more >How can I resolve the error "cannot execute binary file"?
binary file consists of machine instructions the processor can understand. Your operating system does not mean the same executable will run.
Read more >Is the bin/ directory for storing binary files?
No, a bin directory is not for storing only binary files. It's for keeping executable files, primarily. Historically, before scripts written ...
Read more >Why you should not push binary files to git? And what to do if ...
The best idea I recommend you is to store binary files in separate version control system such as Dropbox, Google driver and use...
Read more >How can I handle large binary files (efficiently) with Git LFS?
As a result, these files will not be stored in your local repository, but in a dedicated LFS cache (locally) and store (remotely)....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Nothing dangerous. The only potential problem I see is that if another package (not created with
electron-installed-debian
) has files at/usr/lib/<package>
, then packages that are created withelectron-installer-debian
will fail to install because of conflicting files.Yup, sounds pretty clear. Any dangerous side effects you can think of? If not, feel free to create a PR and I’ll merge it.