In theory we should have used profiles settings for this, providing a proper unity.ini
But right now there's no reason for that effort.
In case someone wants to change settings, profiles will fix this.

In theory we should have used profiles settings for this, providing a proper unity.ini
But right now there's no reason for that effort.
In case someone wants to change settings, profiles will fix this.

methods don't have virtual destructors, added the virtual destructors to
get rid of warnings and potential memory leaks

type from the setting in order to free it properly, just use a stub. Because
the stub can store data properly, we don't need to worry about keeping around
a copy of the list info anymore.

Use prefix instead of postfix de- and increments

(LP: #1173799)

	included in everything.

(LP: #1163611)

Instead declare the variable and assign a value in the same line

* Check if the pointers contain info before freeing

1. Allow us to open ini files we don't have write access to, just complain
about the fact that we can't lock them.
2. Append items to the scandir list correctly
3. Check for existing profiles on the backends before setting
the profile, as the backends may just go ahead and import the new profile
we want to check for if its already set upon calling getExistingProfiles
4. Pass an actual path to ccsImportFromFile
5. Make sure to load plugins up in ccsImportFromFile
6. Write out changed settings in ccsImportFromFile.

Okay, we should be importing profiles available from the sysconfdir scandir () and not yet registered
in the backend

interfaces into ccsEmptyContextNew

the right way after an upgrade

(LP: #1130679)

[  FAILED  ] CCSSettingsUpgradeTestWithMockContext.TestAddValuesInListAppendsValuesToListFromList