Personally I believe extending the setup (as described below) is a must,
in order to change the installer.
On 30/07/2012 14:25, Reinier Olislagers wrote:
I can deal with the installer. but there first must be a solution for
upgrading
I'd suggest we
1. remove existing gdb.exe from the old location
2. check if the setting in (the default?) primary config path points to
the removed gdb.exe
3. change it to the new location
We could probably reuse some code that was used during the last big
settings upgrade (0.9.31? can't remember)
That it was the setup dialog does (for fpc, fpc sources, and lazarus dir)
Run
lazarus.exe --setup
Issue is, I don't have the time to look at it.
It should:
- Check the current config, use it, if it appears ok (potentially run
it, to get the version)
- If there is no environmentoptions.xml in the primary conf, then it
uses secondary conf (the environmentoptions.xml in the exe dir)
- Look in a list of default locations
If it changes existing primary conf, then it should always inform the user
Disadvantage: people with custom gdb.exe will not have it changed
The must have it in a none default location (or it would be
overwritten). So that is simply kept. I see no disadvantage.
But the setup can give them a change to notice the new structure.
Maybe the new structure can also be added to the list of know gdb in the
drop down.
However, the setup dialog is the same for all platforms. So the list of
path to look must be included for the various platforms.
Alternatively, we can just overwrite the user's debugger setting, but
that seems a bit unfriendly as they already changed the default and
presumably know what they're doing.
No way
--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
