lkishalmi commented on PR #75: URL: https://github.com/apache/netbeans-tools/pull/75#issuecomment-2635466418
Well, existing userdir migration path mostly have rules migrating user dirs from NetBeans versions before version 8. Beyond that it marks user downloaded modules and allow them to be copied over to the new userdir. How zip and other installer works is the traditional one. You download the new release and do the install, and all the ceremony with that. (Without a package repository even our Linux packages works that way) Snap, coming from the mobile world, and having a repository, does it the other way around. Many people do not like it as it gives away some freedom and control on the details how the software would be installed. Though it is for the end user experience. So, what Snap does is: It took the `userdir` of the current version and copies that to the new version. Then start the IDE with the newly copied `userdir` and a fresh `cachedir`. This also makes it possible to use `snap revert` to switch back to the previous version if the upgrade would not satisfy the user needs. Also (if not explicitly said so), version upgrades are forced, happens in the background, so usually in a week after every release all Snapped NetBeans users will get the upgrade. I do not know more convenient, user friendly method to install NetBeans. I think patching custom `netbeans.conf`, more suits that philosophy. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
