Hi,as the subject says I'm wondering where I can find the debian directory for tdevelop and be able to build the package(s)? And a second bonus questionI have ported kplayer to tde r14 but I don't know how to upload the modified code. The instructions I received are not clear to me. I also created a debian directory for this, but not sure if it should be uploaded and how to proceed with it. thanks in advance and regards
On Wednesday 08 of July 2015 00:10:54 Emanoil Kotsev wrote:
Hi,as the subject says I'm wondering where I can find the debian directory for tdevelop and be able to build the package(s)? And a second bonus questionI have ported kplayer to tde r14 but I don't know how to upload the modified code. The instructions I received are not clear to me. I also created a debian directory for this, but not sure if it should be uploaded and how to proceed with it. thanks in advance and regards
Very short answer is: take a source code of module from git, include 'debian' folder from tde-packaging git repository, update version in 'changelog' and you can build :)
To maintain the nightly-builds and preliminary-stable-builds repositories of course we have scripts that automate the creation of source packages - especially for maintaining versioning of packages. Unfortunately, these scripts are not yet published. However, you can use the script create-tarball, which can serve as a basis to get 'orig.tar.xz'.
Alternatively, you can use one very simple way - download the source package from the nightly-builds or from preliminary-stable-builds, add a patch to test and build. This is by far the easiest way.
For KPlayer please create a new bug report in Trinity Bugzilla and attach the patch to this bug report.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On 2015/07/08 08:46 AM, Slávek Banko wrote:
On Wednesday 08 of July 2015 00:10:54 Emanoil Kotsev wrote:
Hi,as the subject says I'm wondering where I can find the debian directory for tdevelop and be able to build the package(s)? And a second bonus questionI have ported kplayer to tde r14 but I don't know how to upload the modified code. The instructions I received are not clear to me. I also created a debian directory for this, but not sure if it should be uploaded and how to proceed with it. thanks in advance and regards
Very short answer is: take a source code of module from git, include 'debian' folder from tde-packaging git repository, update version in 'changelog' and you can build :)
I missed the original email from Emanoil..... perhaps something with the ML managing programs (time to time mails bounce back and I do not get them).
In addition to Slavek's reply, here is a simple way to try: 1) download the package code that you want to build from the GIT main repo and copy it somewhere (for example /home/<user>/tde_src/tdevelop) 2) download the package "packaging" code from the GIT packaging repo and copy the "debian"folder for the correct distro into the forder you used in point 1 (for example /home/<user>/tde_src/tdevelop/debian) 3) update change log 4) cd to the folder (cd /home/<user>/tde_src/tdevelop) 5) "debian/rules binary" should work out of the box and build all the required .deb in the parent folder (for example /home/<user>/tde_src), provided you have all required dependency packages installed.
This is just for a temporary local build. If you want a clean build in a separate chroot environment you should use pbuilder or debuild.
To maintain the nightly-builds and preliminary-stable-builds repositories of course we have scripts that automate the creation of source packages - especially for maintaining versioning of packages. Unfortunately, these scripts are not yet published. However, you can use the script create-tarball, which can serve as a basis to get 'orig.tar.xz'.
This is a long outstanding point, we promised several times that we would publish the scripts after R14.0.0 was out but we haven't done it yet.... I will sit down and address this point once I am done with bug 420 (hopefully :-) )
For KPlayer please create a new bug report in Trinity Bugzilla and attach the patch to this bug report.
Please create a new bug and attach both the original code you started from and the final version, so we can also see the changes that were required.
PS: you are more than welcome to contribute to TDE development. Any improvement we can make will benefit the whole community ;-)
Hi and thanks to both of you! My problem is that I am not that good with git and I did only one course with cmake time ago.I prefix my comments with E: inline, because I am not quite sure how nice yahoo formats the mail. I am considering using another e-mail address for the communication with the list.Are you available on gmane? I could not find you there.
On Wednesday, July 8, 2015 5:40 AM, Michele Calgaro michele.calgaro@yahoo.it wrote:
On 2015/07/08 08:46 AM, Slávek Banko wrote:
On Wednesday 08 of July 2015 00:10:54 Emanoil Kotsev wrote:
Hi,as the subject says I'm wondering where I can find the debian directory for tdevelop and be able to build the package(s)? And a second bonus questionI have ported kplayer to tde r14 but I don't know how to upload the modified code. The instructions I received are not clear to me. I also created a debian directory for this, but not sure if it should be uploaded and how to proceed with it. thanks in advance and regards
Very short answer is: take a source code of module from git, include 'debian' folder from tde-packaging git repository, update version in 'changelog' and you can build :)
I missed the original email from Emanoil..... perhaps something with the ML managing programs (time to time mails bounce back and I do not get them). E: This is also bouncing my mails from the yahoo account I use
In addition to Slavek's reply, here is a simple way to try: 1) download the package code that you want to build from the GIT main repo and copy it somewhere (for example /home/<user>/tde_src/tdevelop) E: This I did with GIT_ASKPASS=echo git clone --recursive https://anonymous@scm.trinitydesktop.org/scm/git/tdevelop
After this used cmake to build and it looks it is working fine, so I wanted to have deb packages in order to relpace the R14 jessie ones
2) download the package "packaging" code from the GIT packaging repo and copy the "debian"folder for the correct distro into the forder you used in point 1 (for example /home/<user>/tde_src/tdevelop/debian) E: this is I did with git submodule add http://system@scm.trinitydesktop.org/scm/git/tde-packaging
3) update change log 4) cd to the folder (cd /home/<user>/tde_src/tdevelop) 5) "debian/rules binary" should work out of the box and build all the required .deb in the parent folder (for example /home/<user>/tde_src), provided you have all required dependency packages installed. E: At the moment I wait for downloading the tde-packaging part. I'll take my chance on it next
This is just for a temporary local build. If you want a clean build in a separate chroot environment you should use pbuilder or debuild. E: For now chroot is not in my scope.
To maintain the nightly-builds and preliminary-stable-builds repositories of course we have scripts that automate the creation of source packages - especially for maintaining versioning of packages. Unfortunately, these scripts are not yet published. However, you can use the script create-tarball, which can serve as a basis to get 'orig.tar.xz'.
This is a long outstanding point, we promised several times that we would publish the scripts after R14.0.0 was out but we haven't done it yet.... I will sit down and address this point once I am done with bug 420 (hopefully :-) ) E: I might have raised a bug against tdevelop as recently it started crashing more often with assert on part && parent in fileview. I was able to recover by reimporting the project, but slowly my patience gets at the end.E: I was thinking to build the package and test it as one mentioned going back for the kdevelop etc etc, instead of trying to debug that part of the code. But this is subject of another thread.
For KPlayer please create a new bug report in Trinity Bugzilla and attach the patch to this bug report.
Please create a new bug and attach both the original code you started from and the final version, so we can also see the changes that were required.E:This is much better than originally suggested to use git. I appreciate this as I was not able to follow up the instruction.In fact the porting of the application was not that hard as to understand how to contribute it. I'll try to follow up on that.
PS: you are more than welcome to contribute to TDE development. Any improvement we can make will benefit the whole community ;-) E: I would love to, but time is very limited at the moment, so doing my best. I think it would be of advantage to get a brief process description of and experience with common tasks, like the ones discussed above. I have a lot of experience with debian and very good one with OOP in some languages, but I have just few hours a week left. I hope this will change sooner or later though.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
Hi and thanks to both of you! My problem is that I am not that good with git and I did only one course with cmake time ago.I prefix my comments with E: inline, because I am not quite sure how nice yahoo formats the mail. I am considering using another e-mail address for the communication with the list.Are you available on gmane? I could not find you there.
http://dir.gmane.org/gmane.comp.desktop.trinity.user http://dir.gmane.org/gmane.comp.desktop.trinity.devel
Tim
hi
http://dir.gmane.org/gmane.comp.desktop.trinity.user http://dir.gmane.org/gmane.comp.desktop.trinity.devel
this helped, no idea why I had to click new list to get the groups visible.
thanks
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Still missing Emanoil messages..... :-(
In addition to Slavek's reply, here is a simple way to try: 1) download the package code that you want to build from the GIT main repo and copy it somewhere (for example /home/<user>/tde_src/tdevelop)
E: This I did with GIT_ASKPASS=echo git clone --recursive https://anonymous-24c8wBLmhuFsCdPV93hFxf1oAjcxobwF@public.gmane.org.org /scm/git/tdevelop
After this used cmake to build and it looks it is working fine, so I wanted to have deb packages in order to relpace the R14 jessie ones
OK
- download the package "packaging" code from the GIT packaging repo and copy the "debian"folder for the correct
distro into the forder you used in point 1 (for example /home/<user>/tde_src/tdevelop/debian)
E: this is I did with git submodule add http://system-24c8wBLmhuH1KXRcyAk9cg@public.gmane.orgtydesktop.org/scm/git/t...
I usually keep the tde-packaging as a separate repo instead of a submodule ot the main repo. In any case you need to copy the debian folder as explained before
<snip>
E: I might have raised a bug against tdevelop as recently it started crashing more often with assert on part &&
parent >in fileview. I was able to recover by reimporting the project, but slowly my patience gets at the end.
E: I was thinking to build the package and test it as one mentioned going back for the kdevelop etc etc, instead of trying to debug that part of the code. But this is subject of another thread.
Ok, please report back any info you can gather from testing to the bug report. By the way, what is the bug number you are referring to?
PS: you are more than welcome to contribute to TDE development. Any improvement we can make will benefit the whole community ;-)
E: I would love to, but time is very limited at the moment, so doing my best. I think it would be of advantage to get a brief process description of and experience with common tasks, like the ones discussed above. I have a lot of experience with debian and very good one with OOP in some languages, but I have just few hours a week left. I hope this will change sooner or later though.
No worries, we are more or less in the same situation and can only devote time to TDE when we have it ;-) As introduction to building TDE, have a look at the link below, it should give some more insights although some info may be outdated or partially incorrect (for example we now build using tqt3 instead of qt3) https://wiki.trinitydesktop.org/How_to_Build_TDE_Core_Modules
Cheers Michele
Michele Calgaro wrote:
I usually keep the tde-packaging as a separate repo instead of a submodule ot the main repo. In any case you need to copy the debian folder as explained before
yes I also did so
<snip> > E: I might have raised a bug against tdevelop as recently it started > crashing more often with assert on part && parent >in fileview. I was able to recover by reimporting the project, but slowly my patience gets at the end. > E: I was thinking to build the package and test it as one mentioned going > back for the kdevelop etc etc, instead of trying to debug that part of > the code. But this is subject of another thread. Ok, please report back any info you can gather from testing to the bug report. By the way, what is the bug number you are referring to?
The number is 2475. I can not figure out what is wrong there. To me it looks like something related to events and threads. I think the PHP part is affected as I don't have any issues working with C++ projects. The PHP is failing at random when I open a PHP project, but not if I just open single php files. If you could give me some hint how to debug it would be great.
No worries, we are more or less in the same situation and can only devote time to TDE when we have it ;-) As introduction to building TDE, have a look at the link below, it should give some more insights although some info may be outdated or partially incorrect (for example we now build using tqt3 instead of qt3) https://wiki.trinitydesktop.org/How_to_Build_TDE_Core_Modules
Thanks I already went through this part as I ported the KPlayer to the new TDE.
If you