by Asta666 » 05 Mar 2017, 23:24
Any thoughts or suggestions? Something to do this already existed and I missed it?
by vinnie » 09 Mar 2017, 19:13
I've seen the script but I have not tried it yet, I must say that at first glance I do not have enough knowledge of bash to understand all.
I did not understand what kind of file is "forge.profile.properties", what I think I've figured out is that if you have made changes to the directory as "editions" or "skins", these are lost.
by Asta666 » 09 Mar 2017, 21:18
forge.profile.properties is a file that comes with forge and enables you to use custom directories for storing user data, so IMHO it makes sense to preserve it after an update in case one is using it (I use it actually).
by vinnie » 09 Mar 2017, 22:01
or you can test only a reasonable part of dir, for example I think there are good chances that there are changes in "skin" since it is the themes dir.
However if you do not accept the changes because you think it's better to operate by hand, it would be good still have the old version.
So maybe it would be right to keep the old version instead of deleting it
by Asta666 » 09 Mar 2017, 22:35
Nonetheless you can keep both versions, if you choose no when prompted for replacement the new version is downloaded and extracted to ~/Downloads/Forge and the old one remains unchanged.
by vinnie » 10 Mar 2017, 11:07
I think that should not be the script to determine this, but it should be a choice left to the user.Asta666 wrote:Thanks for your feedback. Yeah and I think another problem in that case would be how to determine the old customisations are compatible with the new release.
I think that automatically determine the compatibility of overwriting is impraticable task
The system that you used has the advantage of never delete the old version if not required.Nonetheless you can keep both versions, if you choose no when prompted for replacement the new version is downloaded and extracted to ~/Downloads/Forge and the old one remains unchanged.
The system that I have suggested has the advantage of being able to create the new version without deleting the old, in theory you should not erase the old version even if you start your script 2 times by mistake, since the script controls the latest version before updating.
by mussol » 21 Apr 2017, 10:43
is really easy to do with something like:
- Code: Select all
- Posts: 2
- Joined: 17 Apr 2017, 14:53
- Has thanked: 0 time
- Been thanked: 0 time
Who is online
Users browsing this forum: friarsol and 8 guests