Here is a link to a 13 MB patch that finishes renaming tdevelop components.
http://humanreadable.nfshost.com/misc/tdevelop-kdev-tdev-rename.diff
There are no build failures or errors or warnings. I don't know how to use tdevelop but my modest tests indicates the patch is stable. You folks who use tdevelop can test more thoroughly and update the patch as needed.
Darrell
.. Why not do this over git instead of emailing a link to a 13mb diff? On Feb 27, 2014 9:45 PM, "Darrell" darrella@clovermail.net wrote:
Here is a link to a 13 MB patch that finishes renaming tdevelop components.
http://humanreadable.nfshost.com/misc/tdevelop-kdev-tdev-rename.diff
There are no build failures or errors or warnings. I don't know how to use tdevelop but my modest tests indicates the patch is stable. You folks who use tdevelop can test more thoroughly and update the patch as needed.
Darrell
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Friday 28 of February 2014 03:47:56 Calvin Morrison wrote:
.. Why not do this over git instead of emailing a link to a 13mb diff?
On Feb 27, 2014 9:45 PM, "Darrell" darrella@clovermail.net wrote:
Here is a link to a 13 MB patch that finishes renaming tdevelop components.
http://humanreadable.nfshost.com/misc/tdevelop-kdev-tdev-rename.diff
There are no build failures or errors or warnings. I don't know how to use tdevelop but my modest tests indicates the patch is stable. You folks who use tdevelop can test more thoroughly and update the patch as needed.
Darrell
I fully understand that Darrell gave first patch for review and commenting than being inadvertently broken GIT tree.
I suppose I'll look at patch on Saturday.
Guys,
BRANCHING IS CHEAP. You branch for a feature, commit to it, push it, then tell others to pull it and test it out... If it works merge it and delete the branch.
I don't think y'all quite grasp the concept On Feb 27, 2014 9:53 PM, "Slávek Banko" slavek.banko@axis.cz wrote:
On Friday 28 of February 2014 03:47:56 Calvin Morrison wrote:
.. Why not do this over git instead of emailing a link to a 13mb diff?
On Feb 27, 2014 9:45 PM, "Darrell" darrella@clovermail.net wrote:
Here is a link to a 13 MB patch that finishes renaming tdevelop components.
http://humanreadable.nfshost.com/misc/tdevelop-kdev-tdev-rename.diff
There are no build failures or errors or warnings. I don't know how to use tdevelop but my modest tests indicates the patch is stable. You
folks
who use tdevelop can test more thoroughly and update the patch as
needed.
Darrell
I fully understand that Darrell gave first patch for review and commenting than being inadvertently broken GIT tree.
I suppose I'll look at patch on Saturday.
-- Slavek
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Thu February 27 2014 9:00:28 pm Calvin Morrison wrote:
Guys,
BRANCHING IS CHEAP. You branch for a feature, commit to it, push it, then tell others to pull it and test it out... If it works merge it and delete the branch.
I don't think y'all quite grasp the concept
A lot of bark for somebody who does no hacking for the project.
Darrell
Doesn't mean I don't understand git. I only comment here on things I think I have a intelligent point to make on things I do have experience.
Ad hominem from you? I didn't expect that. On Feb 27, 2014 10:09 PM, "Darrell" darrella@clovermail.net wrote:
On Thu February 27 2014 9:00:28 pm Calvin Morrison wrote:
Guys,
BRANCHING IS CHEAP. You branch for a feature, commit to it, push it, then tell others to pull it and test it out... If it works merge it and delete the branch.
I don't think y'all quite grasp the concept
A lot of bark for somebody who does no hacking for the project.
Darrell
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Thu February 27 2014 9:16:20 pm Calvin Morrison wrote:
Doesn't mean I don't understand git. I only comment here on things I think I have a intelligent point to make on things I do have experience.
I never wrote you didn't understand git or were wrong. I wrote that you bark a lot and were not producing anything useful for the project.
Ad hominem from you? I didn't expect that.
Exactly what did you expect? I don't expect people to disappear for a year and half only to return and make noise. Kind of irritating to grumpy old men.
Darrell
On Friday 28 of February 2014 04:00:28 Calvin Morrison wrote:
Guys,
BRANCHING IS CHEAP. You branch for a feature, commit to it, push it, then tell others to pull it and test it out... If it works merge it and delete the branch.
I don't think y'all quite grasp the concept
Yes, yes, you're right. Along with Git branching and merging is excellent. However, currently we are not very proficient in working with branches.
Here my usual workflows with my coworkers
$ git branch feature $ git checkout branch
... Edits etc
$ git commit $ got push origin feature
.. mail coworkers to pull and test
To pull
$ git pull origin branch name
On Feb 27, 2014 10:15 PM, "Slávek Banko" slavek.banko@axis.cz wrote:
On Friday 28 of February 2014 04:00:28 Calvin Morrison wrote:
Guys,
BRANCHING IS CHEAP. You branch for a feature, commit to it, push it,
then
tell others to pull it and test it out... If it works merge it and
delete
the branch.
I don't think y'all quite grasp the concept
Yes, yes, you're right. Along with Git branching and merging is excellent. However, currently we are not very proficient in working with branches.
-- Slavek
To unsubscribe, e-mail:
trinity-devel-unsubscribe@lists.pearsoncomputing.net
For additional commands, e-mail:
trinity-devel-help@lists.pearsoncomputing.net
Read list messages on the web archive:
http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Thu February 27 2014 9:20:21 pm Calvin Morrison wrote:
Here my usual workflows with my coworkers
$ git branch feature $ git checkout branch
... Edits etc
$ git commit $ got push origin feature
.. mail coworkers to pull and test
To pull
$ git pull origin branch name
Does this work for a once-only mega-patch that can't be attached to the bugzilla?
How is the branch deleted when the mega-patch is tested and merged into the main trunk?
Darrell
It should work for any size of changes/number of commits and removing it is easy using
$ git branch -d name On Feb 27, 2014 10:36 PM, "Darrell" darrella@clovermail.net wrote:
On Thu February 27 2014 9:20:21 pm Calvin Morrison wrote:
Here my usual workflows with my coworkers
$ git branch feature $ git checkout branch
... Edits etc
$ git commit $ got push origin feature
.. mail coworkers to pull and test
To pull
$ git pull origin branch name
Does this work for a once-only mega-patch that can't be attached to the bugzilla?
How is the branch deleted when the mega-patch is tested and merged into the main trunk?
Darrell
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Thu February 27 2014 8:44:51 pm Darrell wrote:
Here is a link to a 13 MB patch that finishes renaming tdevelop components.
http://humanreadable.nfshost.com/misc/tdevelop-kdev-tdev-rename.diff
When the tdevelop patch is pushed then tdewebdev needs nominal updating:
http://humanreadable.nfshost.com/misc/tdewebdev-tdevelop-renames.diff
Darrell
On Friday 28 of February 2014 03:44:51 Darrell wrote:
Here is a link to a 13 MB patch that finishes renaming tdevelop components.
http://humanreadable.nfshost.com/misc/tdevelop-kdev-tdev-rename.diff
There are no build failures or errors or warnings. I don't know how to use tdevelop but my modest tests indicates the patch is stable. You folks who use tdevelop can test more thoroughly and update the patch as needed.
Darrell
I am just beginning and I noticed two problems:
__1__
-mimedir = $(kde_mimedir)/application +mimedir = $(tde_mimedir)/application
Variable kde_mimedir is defined in the common 'admin' module. Change to tde_mimedir would mean a change first in common 'admin' module and subsequently in all other modules.
__2__
diff -urNa tdevelop/admin/am_edit tdevelop.new/admin/am_edit --- tdevelop/admin/am_edit 2013-12-23 12:30:03.000000000 -0600 +++ tdevelop.new/admin/am_edit 2014-02-27 16:11:26.838531714 -0600 @@ -432,7 +432,7 @@ # some strange people like to do a install-exec, and expect that also # all modules are installed. automake doesn't know this, so we need to move # this here from install-data to install-exec. - if ($MakefileData =~ m/\nkde_module_LTLIBRARIES\s*=/) { + if ($MakefileData =~ m/\ntde_module_LTLIBRARIES\s*=/) { # $target_adds{"install-exec-am"} .= "install-kde_moduleLTLIBRARIES "; # don't use $target_adds here because we need to append the dependency, not # prepend it. Fixes #44342 , when a module depends on a lib in the same dir
Here patch blatantly making a change for the common 'admin' module.
On Saturday 01 of March 2014 18:49:03 Slávek Banko wrote:
On Friday 28 of February 2014 03:44:51 Darrell wrote:
Here is a link to a 13 MB patch that finishes renaming tdevelop components.
http://humanreadable.nfshost.com/misc/tdevelop-kdev-tdev-rename.diff
There are no build failures or errors or warnings. I don't know how to use tdevelop but my modest tests indicates the patch is stable. You folks who use tdevelop can test more thoroughly and update the patch as needed.
Darrell
I am just beginning and I noticed two problems:
__1__
-mimedir = $(kde_mimedir)/application +mimedir = $(tde_mimedir)/application
Variable kde_mimedir is defined in the common 'admin' module. Change to tde_mimedir would mean a change first in common 'admin' module and subsequently in all other modules.
__2__
diff -urNa tdevelop/admin/am_edit tdevelop.new/admin/am_edit --- tdevelop/admin/am_edit 2013-12-23 12:30:03.000000000 -0600 +++ tdevelop.new/admin/am_edit 2014-02-27 16:11:26.838531714 -0600 @@ -432,7 +432,7 @@ # some strange people like to do a install-exec, and expect that also # all modules are installed. automake doesn't know this, so we need to move # this here from install-data to install-exec.
- if ($MakefileData =~ m/\nkde_module_LTLIBRARIES\s*=/) {
- if ($MakefileData =~ m/\ntde_module_LTLIBRARIES\s*=/) {
# $target_adds{"install-exec-am"} .= "install-kde_moduleLTLIBRARIES "; # don't use $target_adds here because we need to append the dependency, not # prepend it. Fixes #44342 , when a module depends on a lib in the same dir
Here patch blatantly making a change for the common 'admin' module.
I looked a little further - it seems that these variables can not be renamed without changes in the global admin module:
tde_appsdir tde_confdir tde_includes tde_mimedir tde_module tde_moduledir tde_servicesdir tde_servicetypesdir
I looked a little further - it seems that these variables can not be renamed without changes in the global admin module:
tde_appsdir tde_confdir tde_includes tde_mimedir tde_module tde_moduledir tde_servicesdir tde_servicetypesdir
I presume you have already updated your copy of the patch. I reverted those here and tdevelop built and ran with no issues. Unfortunately, my build script no longer supports building tdevelop with autotools, which I would need to test the above changes. I could look through my backups and restore the autotools support and test again.
After reverting the above I diff'd common/admin to tdevelop.new/admin. They are the same.
Anyway here is the updated patch:
http://humanreadable.nfshost.com/misc/tdevelop-kdev-tdev-rename-2.diff
Yet even after validating the compilation is okay, you tdevelop gurus will need to test usability that nothing is harmed.
Darrell
On 03/01/2014 01:30 PM, Darrell wrote:
I presume you have already updated your copy of the patch. I reverted those here and tdevelop built and ran with no issues. Unfortunately, my build script no longer supports building tdevelop with autotools, which I would need to test the above changes. I could look through my backups and restore the autotools support and test again.
After reverting the above I diff'd common/admin to tdevelop.new/admin. They are the same.
Anyway here is the updated patch:
http://humanreadable.nfshost.com/misc/tdevelop-kdev-tdev-rename-2.diff
Yet even after validating the compilation is okay, you tdevelop gurus will need to test usability that nothing is harmed.
I'll give it a try, but there is a great little tutorial that will walk you though it that is instrumental in understanding (from a very basic standpoint) tde applications and how the parts of kdevelop work:
http://techbase.kde.org/Development/Tutorials/KDE3/Qt_Designer_and_KDevelop_...
Well worth doing for multiple reasons..
On Saturday 01 of March 2014 20:30:38 Darrell wrote:
I looked a little further - it seems that these variables can not be renamed without changes in the global admin module:
tde_appsdir tde_confdir tde_includes tde_mimedir tde_module tde_moduledir tde_servicesdir tde_servicetypesdir
I presume you have already updated your copy of the patch. I reverted those here and tdevelop built and ran with no issues. Unfortunately, my build script no longer supports building tdevelop with autotools, which I would need to test the above changes. I could look through my backups and restore the autotools support and test again.
After reverting the above I diff'd common/admin to tdevelop.new/admin. They are the same.
Anyway here is the updated patch:
http://humanreadable.nfshost.com/misc/tdevelop-kdev-tdev-rename-2.diff
Yet even after validating the compilation is okay, you tdevelop gurus will need to test usability that nothing is harmed.
Darrell
Because I can easily test building with CMake and also with autotools, I tested both. Because of this I found two more trouble renaming: tde_bin* and tde_service*. After revert these renaming I am building successfully with both. I think then push the patch.
Because I can easily test building with CMake and also with autotools, I tested both. Because of this I found two more trouble renaming: tde_bin* and tde_service*. After revert these renaming I am building successfully with both. I think then push the patch.
I checked my backups as far back as one year and I don't have autotools support. tdevelop must have been one of the first modules that was converted to cmake.
Push when you are comfortable.
I have a list of small patches that need to be made after pushing the tdevelop patch.
We need to update r14-xdg-update to rename kdev* -> tdev* user config files.
Darrell
On Sunday 02 of March 2014 19:34:13 Darrell wrote:
Because I can easily test building with CMake and also with autotools, I tested both. Because of this I found two more trouble renaming: tde_bin* and tde_service*. After revert these renaming I am building successfully with both. I think then push the patch.
I checked my backups as far back as one year and I don't have autotools support. tdevelop must have been one of the first modules that was converted to cmake.
Push when you are comfortable.
I have a list of small patches that need to be made after pushing the tdevelop patch.
We need to update r14-xdg-update to rename kdev* -> tdev* user config files.
Darrell
tdevelop patch pushed to GIT in hash 722ce1ef.
How with patch for tdewebdev? You're going to push?
tdevelop patch pushed to GIT in hash 722ce1ef.
How with patch for tdewebdev? You're going to push?
Here is my short list of addendum changes:
tdeaccessibility/IconThemes/mono/scalable/apps/kdevassistant.svgz tdeaccessibility/IconThemes/mono/scalable/apps/kdevdesigner.svgz tdeaccessibility/IconThemes/mono/scalable/apps/kdeapp.svgz *.kdevses *.kdevelop* *.kdevprj *.kdev_* *.kdevtemplate kdapp->tdeapp tde-i18n: kdevdesigner.po, kdevtipofday.po tdeconf_update scripts r14-xdg-update: $TDEHOME/share/config/kdev*->tdev* $TDEHOME/share/apps/kdev*->tdev*
I can perform most of this cleanup. First I need to download the tdevelop changes and rebuild. Then I can methodically watch what fails with my next full build run.
Regarding tdeconf_update scripts, refer to bug report 1985:
http://bugs.trinitydesktop.org/show_bug.cgi?id=1985
There like are more such nominal changes. One step at a time.
Darrell
tdevelop patch pushed to GIT in hash 722ce1ef.
I noticed this before: When I open TDevelop Designer, in the left-side Common Widgets pane, several buttons have a "(KDE)" suffix. Is there a way to change that to TDE? I looked and did not find anything obvious.
Darrell
tdevelop patch pushed to GIT in hash 722ce1ef.
I am working on follow-up details. I notice the following:
tdevelop/languages/cpp/app_templates/kdevlang tdevelop/languages/cpp/app_templates/kdevpart tdevelop/languages/cpp/app_templates/kdevpart2
tdevelop/languages/cpp/app_templates/tdevlang tdevelop/languages/cpp/app_templates/tdevpart tdevelop/languages/cpp/app_templates/tdevpart2
Numerous .kdev_ignore not renamed to .tdev_ignore.
Were these files and directories intentionally left as-is or did we simply overlook them?
Darrell
tdevelop patch pushed to GIT in hash 722ce1ef.
Looks like the following might remain throughout the git tree. Do any of these matter? Leave as is?
*.kdevses *.kdevprj *.kdevelop.pcs *.kdevelop.spec kdevdlg* tdeconf_update scripts
Darrell
-
Calvin Morrison -
Darrell -
David C. Rankin -
Slávek Banko