Hi, I've recently subscribed to Trinity mailing lists, and would like to introduce myself. As many others here, I'm a long time KDE user. I don't want to rant about the current state of KDE4; let's just say that now I feel no more "at home" in KDE community.
I like the ideas and spirit of the Trinity project, so I would like to offer some help in my spare time... which is unfortunately very few. :(
But anyway, at work I maintain a minimal, server-oriented openSUSE derivate distribution, so I know how to manage RPMs, specfiles, and building problems. And I've also worked to projects both in C and C++ some years ago, so I hope to contribute some bug squashing too.
I would like to help with RPM packaging for openSUSE. In the OBS site I've found the projects by Robert Xu. Are there other efforts or other people working on it? May I ask what is the current state, and how can I help?
Sincerely Andrea Cascio
Hi, I've recently subscribed to Trinity mailing lists, and would like to introduce myself. As many others here, I'm a long time KDE user. I don't want to rant about the current state of KDE4; let's just say that now I feel no more "at home" in KDE community.
I like the ideas and spirit of the Trinity project, so I would like to offer some help in my spare time... which is unfortunately very few. :(
But anyway, at work I maintain a minimal, server-oriented openSUSE derivate distribution, so I know how to manage RPMs, specfiles, and building problems. And I've also worked to projects both in C and C++ some years ago, so I hope to contribute some bug squashing too.
I would like to help with RPM packaging for openSUSE. In the OBS site I've found the projects by Robert Xu. Are there other efforts or other people working on it? May I ask what is the current state, and how can I help?
Sincerely Andrea Cascio
Hi Andrea,
Welcome!
Timothy Pearson is the Big Kahuna.
There are some OpenSuse folks hanging out here. They likely will see your introduction and reply to you.
We do need people with a C++ background to help with the bug quashing. Right now Tim is in a big SVN-to-GIT conversion and file renaming effort. When that is completed he then will reopen the source tree and everybody who is able will start merging patches upstream and start hacking at the bugzilla.
We also need usability testing.
There is a lot going on right now. We're all anxiously awaiting Tim's work but we also are working toward reorganizing the web site and wiki. We tend to keep project information files and status in etherpad.
There is much to do if you want to jump in anywhere. :)
Darrell
On Wed, Nov 16, 2011 at 09:32, Andrea Cascio andrea@nucleus.it wrote:
Hi, I've recently subscribed to Trinity mailing lists, and would like to introduce myself. As many others here, I'm a long time KDE user. I don't want to rant about the current state of KDE4; let's just say that now I feel no more "at home" in KDE community.
I like the ideas and spirit of the Trinity project, so I would like to offer some help in my spare time... which is unfortunately very few. :(
But anyway, at work I maintain a minimal, server-oriented openSUSE derivate distribution, so I know how to manage RPMs, specfiles, and building problems. And I've also worked to projects both in C and C++ some years ago, so I hope to contribute some bug squashing too.
I would like to help with RPM packaging for openSUSE. In the OBS site I've found the projects by Robert Xu. Are there other efforts or other people working on it? May I ask what is the current state, and how can I help?
Sincerely Andrea Cascio
Hi Andrea, welcome to Trinity!
There are a lot of projects that I have on the OBS, but half of them are unmaintained, so don't go by them ;)
I've been working on getting much of my work up to speed and working again after my dev machine crashed. I thought that I would be able to retrieve a lot of my work, but that didn't happen as much as I thought to plan >_>;;.
I made a branch on the Trinity Desktop tde-packaging git, you can check it out on the suse branch. I'll be updating it as I get to packages. There are handy macros if you want to help :) I've been taking them from the KDE:KDE3 repo and restructuring the packages, removing old/obsoleted patches and other cruft.
I upload them from the GIT to the OBS when I have time. If you need me to upload anything for building, feel free to ask :) (osc build is a good option though >_>)
On Wed, Nov 16, 2011 at 13:13, Robert Xu robxu9@gmail.com wrote:
I upload them from the GIT to the OBS when I have time. If you need me to upload anything for building, feel free to ask :) (osc build is a good option though >_>)
Oh, before I go and forget everything I was just thinking: If you have a iChain account, feel free to let me know your username and I can add you as maintainer for the OBS project so that you can trigger and upload builds :)
On Wednesday 16 November 2011 20:41:55 Robert Xu wrote:
On Wed, Nov 16, 2011 at 13:13, Robert Xu robxu9@gmail.com wrote:
I upload them from the GIT to the OBS when I have time. If you need me to upload anything for building, feel free to ask :) (osc build is a good option though >_>)
Oh, before I go and forget everything I was just thinking: If you have a iChain account, feel free to let me know your username and I can add you as maintainer for the OBS project so that you can trigger and upload builds :)
Excellent idea. My OBS account is "Vajsravana".
Andrea
Hi Andrea, welcome to Trinity!
There are a lot of projects that I have on the OBS, but half of them are unmaintained, so don't go by them ;)
So the right repo is tde3.5.13, not the one that will "destroy my cat", ok? ;)
I've been working on getting much of my work up to speed and working again after my dev machine crashed. I thought that I would be able to retrieve a lot of my work, but that didn't happen as much as I thought to plan >_>;;.
I made a branch on the Trinity Desktop tde-packaging git, you can check it out on the suse branch. I'll be updating it as I get to packages.
Yes, got it. Now, I hope you will advice me, regarding the correct way to work with it. Should I make my own branch or track your suse branch or work on your branch locally than sending you the patches? Sorry if the question sounds stupid but I'm just a beginner with GIT.
There are handy macros if you want to help :) I've been taking them from the KDE:KDE3 repo and restructuring the packages, removing old/obsoleted patches and other cruft.
Still, there are much more patches than I expected, expecially in core packages. Oh well, more patches, more glory. :) Something to start with: if I understand correctly "qt3-3.3.8d" is absolutely required, the qt3-3.3.8c maintained in the standard openSUSE repo won't do the job, right? Do you mind if I try to get a working package for it, as a start? The one on the OBS does not appear to build.
I upload them from the GIT to the OBS when I have time. If you need me to upload anything for building, feel free to ask :) (osc build is a good option though >_>)
I have sent my account. :)
Andrea
PS Oh, and BTW thank you all for your kind welcome. :)
On Wed, Nov 16, 2011 at 18:16, Andrea Cascio andrea@nucleus.it wrote:
So the right repo is tde3.5.13, not the one that will "destroy my cat", ok? ;)
Yup ;) Right now qt3 is only in there >_> and there are patches to remove from it. However, arts, libtqt4, and the dbus bindings are finished and tested, so that can be uploaded ASAP (when qt3 succeeds in building).
Yes, got it. Now, I hope you will advice me, regarding the correct way to work with it. Should I make my own branch or track your suse branch or work on your branch locally than sending you the patches? Sorry if the question sounds stupid but I'm just a beginner with GIT.
Don't worry, no question is stupid :) You can track my suse branch, makes life so much easier :) I use Eclipse with the RPM Spec file editor plugin, so you might see some metadata files there; feel free to ignore them. (I have on record everything to tdebase (kdebase), which means other core apps can be packaged. I have created the directories necessary for them already, so all that's left is importing and modifying)
In .gitignore, I set ignore to backup files (~), _service:*, and .osc, so if you initialize osc in any of the directories, rest assured, nothing will be sent to git :)
There is a package called tde-packaging that I will push ASAP. It contains all your %_tde_prefix and %_tde_bindir and handy directory macros that makes packaging so much easier. In addition, when you are calling cmake, use the following:
%cmake_tde -d build -- -DSOMEOPTION=ON
%make_tde -d build
%makeinstall_tde -d build
This ensures that everything is properly built in the right prefixes and build directories. :) No need to set cmake prefix or anything, that is what %cmake_tde is for. (btw, if you want to specify any extra cmake options, you need the --)
Still, there are much more patches than I expected, expecially in core packages. Oh well, more patches, more glory. :) Something to start with: if I understand correctly "qt3-3.3.8d" is absolutely required, the qt3-3.3.8c maintained in the standard openSUSE repo won't do the job, right? Do you mind if I try to get a working package for it, as a start? The one on the OBS does not appear to build.
Sure. I started removing some of the "already applied" patches, feel free to finish that. I'll throw up tde-packaging and the dependencies on the OBS.
I have sent my account. :)
Got it :D
On Thursday 17 November 2011 00:33:44 Robert Xu wrote:
On Wed, Nov 16, 2011 at 18:16, Andrea Cascio andrea@nucleus.it wrote:
So the right repo is tde3.5.13, not the one that will "destroy my cat", ok? ;)
Yup ;) Right now qt3 is only in there >_> and there are patches to remove from it. However, arts, libtqt4, and the dbus bindings are finished and tested, so that can be uploaded ASAP (when qt3 succeeds in building).
Yes, got it. Now, I hope you will advice me, regarding the correct way to work with it. Should I make my own branch or track your suse branch or work on your branch locally than sending you the patches? Sorry if the question sounds stupid but I'm just a beginner with GIT.
Don't worry, no question is stupid :) You can track my suse branch, makes life so much easier :) I use Eclipse with the RPM Spec file editor plugin, so you might see some metadata files there; feel free to ignore them. (I have on record everything to tdebase (kdebase), which means other core apps can be packaged. I have created the directories necessary for them already, so all that's left is importing and modifying)
In .gitignore, I set ignore to backup files (~), _service:*, and .osc, so if you initialize osc in any of the directories, rest assured, nothing will be sent to git :)
There is a package called tde-packaging that I will push ASAP. It contains all your %_tde_prefix and %_tde_bindir and handy directory macros that makes packaging so much easier. In addition, when you are calling cmake, use the following:
%cmake_tde -d build -- -DSOMEOPTION=ON
%make_tde -d build
%makeinstall_tde -d build
This ensures that everything is properly built in the right prefixes and build directories. :) No need to set cmake prefix or anything, that is what %cmake_tde is for. (btw, if you want to specify any extra cmake options, you need the --)
Still, there are much more patches than I expected, expecially in core packages. Oh well, more patches, more glory. :) Something to start with: if I understand correctly "qt3-3.3.8d" is absolutely required, the qt3-3.3.8c maintained in the standard openSUSE repo won't do the job, right? Do you mind if I try to get a working package for it, as a start? The one on the OBS does not appear to build.
Sure. I started removing some of the "already applied" patches, feel free to finish that.
Many thanks for the help Robert! Ok, now I finally have a coherent set of patches. Many of them are just for specific builds, but it seems to me that some should be included in the main tree. Anyway, I don't know the codebase enough. :)
Just 2 questions left: - are the translations in qt3-3.3.8b-translations still good for 3.3.8d? - it seems that the patch gcc46.diff is only halfway applied in the tarball of 3.3.8d. The part which includes <cstddef> is there, but the part wich converts ptrdiff_t into std::ptrdiff_t is not. I'd keep the patch cutting away the first part, ok?
Tomorrow I will try to get a set of successful OBS builds, let's start populating that repo. :)
Andrea
On Fri, Nov 18, 2011 at 18:56, Andrea Cascio andrea@nucleus.it wrote:
Many thanks for the help Robert! Ok, now I finally have a coherent set of patches. Many of them are just for specific builds, but it seems to me that some should be included in the main tree. Anyway, I don't know the codebase enough. :)
Well, we can examine them :P Some of them I have noticed could be good for qt3.
Just 2 questions left:
- are the translations in qt3-3.3.8b-translations still good for 3.3.8d?
Should be.
- it seems that the patch gcc46.diff is only halfway applied in the tarball of
3.3.8d. The part which includes <cstddef> is there, but the part wich converts ptrdiff_t into std::ptrdiff_t is not. I'd keep the patch cutting away the first part, ok?
That's fine, I know qt 3.3.8d had some gcc46 fixes.
Tomorrow I will try to get a set of successful OBS builds, let's start populating that repo. :)
:D It's the weekend, so I should be able to continue working on packaging. Until Sunday. >_> Then it's all hell breaks loose until Wednesday night... sigh.
On Saturday 19 November 2011 01:01:00 Robert Xu wrote:
On Fri, Nov 18, 2011 at 18:56, Andrea Cascio andrea@nucleus.it wrote:
Many thanks for the help Robert! Ok, now I finally have a coherent set of patches. Many of them are just for specific builds, but it seems to me that some should be included in the main tree. Anyway, I don't know the codebase enough. :)
[...]
It's the weekend, so I should be able to continue working on packaging. Until Sunday. >_> Then it's all hell breaks loose until Wednesday night... sigh.
Thanks god it's weekend here too :D , so finally we have some updated qt3 packages for openSUSE :) I have commited to the OBS, and it's completing the build, I still don't know how to force the build of "extensions" and "devel-doc" but at least the core packages are ready for testing.
If you approve, can you commit to GIT?
Now, I have some question for people on the list: If I understand correctly, qt3-3.3.8d is GPL only, isn't it? Should I edit the specfile removing references to QPL and the lines about "buying licenses from Trolltech"?
I had a problem with qt3-extensions: the specfile builds a qt3-unixODBC subpackage, and of course requires unixODBC-devel. Ok, but 3.3.8d (unlike 3.3.8b/c!) links libiodbc, that come from iODBC, which in turn "conflicts" unixODBC. 2 solutions here: - drop qt3-unixODBC and build a qt3-iodbc. - revert the change that included iodbc in the dependencies.
I've chosen the second, because seems a bit more conservative. The new patch, for opensuse builds, is revert-iodbc-to-uodbc.diff, I hope it does not broke something else in the SQL part.
A final note: src/kernel/qtkdeintegration_x11.cpp src/kernel/qtkdeintegration_x11_p.h Is name correct? Not qttdeintegration_x11.cpp?
So, what now Robert? :) tdelibs? Seems though...
Andrea
On Sat, Nov 19, 2011 at 19:25, Andrea Cascio andrea@nucleus.it wrote:
On Saturday 19 November 2011 01:01:00 Robert Xu wrote:
On Fri, Nov 18, 2011 at 18:56, Andrea Cascio andrea@nucleus.it wrote:
Many thanks for the help Robert! Ok, now I finally have a coherent set of patches. Many of them are just for specific builds, but it seems to me that some should be included in the main tree. Anyway, I don't know the codebase enough. :)
[...]
It's the weekend, so I should be able to continue working on packaging. Until Sunday. >_> Then it's all hell breaks loose until Wednesday night... sigh.
Thanks god it's weekend here too :D , so finally we have some updated qt3 packages for openSUSE :) I have commited to the OBS, and it's completing the build, I still don't know how to force the build of "extensions" and "devel-doc" but at least the core packages are ready for testing.
I can do that.
If you approve, can you commit to GIT?
Sure
Now, I have some question for people on the list: If I understand correctly, qt3-3.3.8d is GPL only, isn't it? Should I edit the specfile removing references to QPL and the lines about "buying licenses from Trolltech"?
That's a good idea, go ahead.
I had a problem with qt3-extensions: the specfile builds a qt3-unixODBC subpackage, and of course requires unixODBC-devel. Ok, but 3.3.8d (unlike 3.3.8b/c!) links libiodbc, that come from iODBC, which in turn "conflicts" unixODBC. 2 solutions here:
- drop qt3-unixODBC and build a qt3-iodbc.
- revert the change that included iodbc in the dependencies.
I've chosen the second, because seems a bit more conservative. The new patch, for opensuse builds, is revert-iodbc-to-uodbc.diff, I hope it does not broke something else in the SQL part.
I trust you :)
A final note: src/kernel/qtkdeintegration_x11.cpp src/kernel/qtkdeintegration_x11_p.h Is name correct? Not qttdeintegration_x11.cpp?
That's still correct for now.
So, what now Robert? :) tdelibs? Seems though...
Yup, I'll push arts and tqtinterface (libtqt4) right away so that we can start on tdelibs.
Le 20/11/2011 01:25, Andrea Cascio a écrit :
Now, I have some question for people on the list: If I understand correctly, qt3-3.3.8d is GPL only, isn't it? Should I edit the specfile removing references to QPL and the lines about "buying licenses from Trolltech"?
If so, here is a patch for the configure script that may help: http://bugs.pearsoncomputing.net/attachment.cgi?id=128
On Wednesday 16 November 2011 09:32:08 am Andrea Cascio wrote:
Hi, I've recently subscribed to Trinity mailing lists, and would like to introduce myself. As many others here, I'm a long time KDE user. I don't want to rant about the current state of KDE4; let's just say that now I feel no more "at home" in KDE community.
I like the ideas and spirit of the Trinity project, so I would like to offer some help in my spare time... which is unfortunately very few. :(
A lot of us can relate to that. Most of us don't want to use KDE4 for one reason or another, and we can't sit wide-eyed and drooling at the computer as much as we'd like ;-)
But anyway, at work I maintain a minimal, server-oriented openSUSE derivate distribution, so I know how to manage RPMs, specfiles, and building problems. And I've also worked to projects both in C and C++ some years ago, so I hope to contribute some bug squashing too.
I would like to help with RPM packaging for openSUSE. In the OBS site I've found the projects by Robert Xu. Are there other efforts or other people working on it? May I ask what is the current state, and how can I help?
Robert would be the one to ask about the openSUSE packages. From what I've seen, his OBS always seems struggling with one issue or another. Even if he has it working, I'm sure he could use the help. We also have a few people trying to get packages going for several other RPM-based distros, if you don't mind helping with those.
Bug squashing and testing is also welcome. Once the migration from svn to git is done, development should start for the next release.
There's normally a monthly developer meeting on Freenode IRC. The last one was a few days ago, so the next one should be in December. It hasn't been scheduled yet, but it would be a good idea to attend to help stay up-to-date on the latest goals and provide your own feedback.
-
Andrea Cascio -
Darrell Anderson -
Kristopher John Gamrat -
Laurent Dard -
Robert Xu