-
Notifications
You must be signed in to change notification settings - Fork 32
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
bundle as linux tar #714
base: master
Are you sure you want to change the base?
bundle as linux tar #714
Conversation
Tested Environment:
NW 64-Bit Build
NW 32-Bit BuildElectron 64-Bit Build❌ Could not be started, probably because some files in the bundle needs certain permissions before getting bundled in a Electron 32-Bit BuildElectron ARM Buildsℹ️ Could not be tested due to lack of hardware with corresponding architecture. |
When deploying |
The |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems the topic needs some more honing and testing on linux platforms before an NW or Electron canary bundle can be released to the public
yea, i have no clue what im doing tbh, i just wanted a build that worked on linux |
as the title says its some bundles for Linux tar
made them not portable because they will be more useful as not portable in regards to external builds
(like the AURs PKGBUILD)
the icon and desktop entry files should probably not be in the tar and instead in a separate linux-assets.tar.gz
i don't plan to maintain this, was just something i wanted to do cause someone asked for a linux release in the discord
though its almost a copy of the windows portable zip so it shouldn't be to bad