inav-configurator
inav-configurator copied to clipboard
iNavFlight
Windows Installer / Linux packages
A scriptable install system (Nullsoft / InnoSetup) under Windows and packages for Linux (rpm / deb) could easily be integrated into gulp and would make installation under windows easier.
easier than just opening the zip file and dragging the folder somewhere ?
On Mon, 28 Feb 2022 at 12:32, Andi Kanzler @.***> wrote:
A scriptable install system (Nullsoft / InnoSetup) could easily be integrated into gulp and would make installation under windows easier.
— Reply to this email directly, view it on GitHub https://github.com/iNavFlight/inav-configurator/issues/1472, or unsubscribe https://github.com/notifications/unsubscribe-auth/AALNCAILH76H6YJUN46IR3DU5OWTXANCNFSM5PRW7T6Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message ID: @.***>
The uninstaller would also clean up and not leave any "corpses" in the user directory.
the issue i can see with uninstallers is that it can only uninstall what it put there (ie what it knows about). that's why windows leaves a whole bunch of crap in program-files et al when you uninstall an app if the application has created files in there that are not in the installer log.
On Mon, 28 Feb 2022 at 12:37, Andi Kanzler @.***> wrote:
The uninstaller would also clean up and not leave any "corpses" in the user directory.
— Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you commented.Message ID: @.***>
Just an idea, it is not really necessary, it is just a function for convenience.
The thing with Installer/Uninstaller is that it makes having multiple versions on one machine much harder.
Two versions of distributions for every OS should be released. One as a .zip, lets call it 'portable', for users want to have several version at a time (btw, this is not problem for MacOS as you can have as many version as want even using installer). Next one, lets call it 'installer', as package (.exe .deb .rpm. dmg), for users who prefer this method.
@DzikuVx In addition, there is nothing impossible to have multiple versions at same time even with installer for Linux and Windows too. For Windows - target installation folder and App UUID need to be changed every release (tested and ok). For LinuX - only target folder (not tested, but I believe it will work). It just requires some additional effort preparing first RC.
https://github.com/iNavFlight/inav-configurator/pull/1541 prepared and tested, for all platforms.
For LinuX - only target folder (not tested, but I believe it will work).
it works, I have an old version for a CC3D :)
For LinuX - only target folder (not tested, but I believe it will work).
it works, I have an old version for a CC3D :)
sure!
anyway, every user can choose preferred distribution, as every have own preferences, so we don't need to stop releasing .zip's or like that. For build script it is not big job to make both :)
Proposed PR are for unified uuid/name/folder (as, for. ex. BF do it now), but as I described before - I will add "differences" if we (dev's) decide that it needed and worth effort.
Having a .deb will make it possible to install and use INAV on Chromebooks, perfect field companions, much easier.
Once installed with .deb, it is possible to launch the configurator app from quick search and/or pin it to the launch bar, instead of digging in the terminal.
Telling from experience with latest BF, installed from .deb
To install deb on Chromebook, one needs enable "Linux development environment", but that's minor.
