| Summary: | TDevelop can not open/create projects after last round of renames | ||
|---|---|---|---|
| Product: | TDE | Reporter: | Michele Calgaro <michele.calgaro> |
| Component: | other (any) | Assignee: | Michele Calgaro <michele.calgaro> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | CC: | bugwatch, darrella, kb9vqf, michele.calgaro, slavek.banko |
| Priority: | P5 | ||
| Version: | R14.0.0 [Trinity] | ||
| Hardware: | Other | ||
| OS: | Linux | ||
| Compiler Version: | TDE Version String: | ||
| Application Version: | Application Name: | ||
| Bug Depends on: | |||
| Bug Blocks: | 2014 | ||
|
Description
Michele Calgaro
2014-03-06 23:27:25 CST
Look inside all of the related tdevelop config files. If possible, post copies of the config files. My initial hunch is there are remnants inside the config files that need to be renamed, just like the config files themselves. Much of the r14-xdg-update script does this same type of internal renaming with other config files. I just got a rather nasty Email on this topic a few days ago. If possible we should maintain full compatibility with the old KDevelop project file syntax; I see no reason to change it and users are rather vocal (and justified!) about this breakage. > If possible we should maintain full compatibility with the old KDevelop
> project file syntax.
Sounds good to me too. As a short term solution I propose we revert the last commit(s) were renaming was involved and that broke compatibility.
As a long term view, if we want to use a new TDE style syntax for TDevelop files, we should add to TDevelop the capability to open both old (KDE style) format and new (TDE style) format and then automatically handle the conversion to the TDE one.
Or we can simply forget about it and keep using the KDevelop format also in the future.
Tim, reverting commits f4487e5, 7fc4617, 2c24100, 5628374, 722ce1e (main) and ab813fb (packaging for Debian/Ubuntu) is enough to bring TDevelop back to a working state and being able to open KDevelop project file. Should I push to GIT? Since there has been no complains to reverting the commits mentioned in comment 4, I have pushed the changes. The commits have been reverted as follow: (main repo) 6392f5a Reverts commit 722ce1e aba2788 Reverts commit 5628374 b664098 Reverts commit 2c24100 41f7ca9 Reverts commit 7fc4617 fc09bfc Reverts commit f4487e5 (packaging repo) 59f50d7 Reverts commit ab813fb TDevelop can now open KDevelop project files again :) The changes related to bug 1860 that were part of commit 722ce1e will be mostly applied in a separate commit when I address that bug. As mentioned in comment 3, if in the long term we plan for a full application set rebranding, we will have to address the issue of maintaining compatibility with KDevelop project file format. I'm afraid we will need to revert some changes that I made in a recent large commit in tde-packaging. > I'm afraid we will need to revert some changes that I made in a recent large
> commit in tde-packaging.
Slavek, before pushing to GIT, I did a full rebuild using the latest GIT sources (including the changes you pushed yesterday to tde-packaging).
After the built and some brief testing, I didn't notice particular problems.
If you are aware of some specific ones, just reopen the report and let me know what needs to be fixed.
(In reply to Michele Calgaro from comment #7) > > I'm afraid we will need to revert some changes that I made in a recent large > > commit in tde-packaging. > Slavek, before pushing to GIT, I did a full rebuild using the latest GIT > sources (including the changes you pushed yesterday to tde-packaging). > After the built and some brief testing, I didn't notice particular problems. > If you are aware of some specific ones, just reopen the report and let me > know what needs to be fixed. Done in commit dda7ef94 (tde-packaging). |