User forums > Help

Upgrading the nightly?

(1/2) > >>

mroek:
Ok, this may be a stupid question, but anyway:

What do you guys do when you want to upgrade to a newer nightly? Do you just unpack the new nightly over the previous one, or do you put it in a separate folder? What happens to the settings? AFAIK, the settings are stored elsewhere (Application Data/codeblocks), but what if the new nightly implements a new or changes a existing setting? Will it just silently upgrade the settings file, and thereby breaking compatibilty with the previous nightly, which in turn renders it meaningless to keep more than one nightly?

David Perfors:
I move the old nightly to a directory old, and unpack the new nightly to the default folder...

killerbot:
you can overwrite one nightly with another (just don't mix with RC2).
you can also put it in a new dir, because the settings are
 a) in the profile folder
 b) registry

Only part b) is a bit annoying if you put it in another dir (not 100% sure anymore) since the codeblocks.exe in your old dir is registered for the CB files (.cpp, . cbp, ...) and not your new one. So either it is done by CB at start=uo (see env settings).
Because of this it is most easiest to install in the same directory (well you can empty the directory first).

When a new seting is created, or some setting changes meaning, or sometimes thourhg an update in the code, it might be needed from time to time to erase some part from default.conf or erase it completely. But this happens only occasionaly.

thomas:
(already answered)
Unpacking one nightly build over another (unlike unpacking a nightly build over RC2!) should work safely, although it is of course always safer to first delete everything or use a separate folder.

Settings, as you said, are stored in your application data folder, so you don't need to worry about that.
99.9% of the time, settings will either be backwards-compatible, or will use different keys, so they do not interfere with older keys. We try to always keep everything as compatible as possible.
As a consequence, it may happen that your configuration carries along a few kilobytes of payload after a few weeks, but that should usually not be a massive problem. Losing configuration is the worse alternative.
It is not necessary to delete parts of the configuration file. Don't even think about such things, you risk to break something, and the possible gains are neglegible. Your PC won't care about +/- 20 kilobytes, and the performance overhead is barely measurable.

But of course, having said "99.9%", there are no guarantees on anything. Remember we're talking about a development version, so we make no claims about consistency between versions.

mroek:
Ok, thanks a lot for your elaborate answers. I will just keep using the same folder for new nightlies, but I will empty it first, just for good measure...  :-)

Navigation

[0] Message Index

[#] Next page