I have now successfully packaged the following for Arch Linux with the PKGBUILDs and some bash scripts for building this set. They will need to be built using a clean chroot see this link for explaination: https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_Clean_Chroo... The PKGBUILD script will show the dependencies for each package. I will moving on to the applications shortly, I need a little break ;)
If anyone is interested i have placed the scripts here: git clone https://github.com/baho-utot/trinity.git until they can be incorperated into the tde-packaging repo.
# # Dependencies # qt3 - autotools - complete tqtinterface - cmake - complete arts - cmake - complete dbus-tqt - cmake - complete dbus-1-tqt - cmake - complete # # Desktop # kdelibs - cmake - complete kdebase - cmake - complete kdebindings - not needed - not needed kdeaccessibility- autotools - complete kdeutils - autotools - complete kdemultimedia - autotools - complete kdeadmin - autotools - complete kdeartwork - autotools - complete kdegames - autotools - complete kdetoys - autotools - complete kdeedu - autotools - complete kdepim - cmake - complete kdesdk - autotools - complete kdeaddons - autotools - complete kdevelop - cmake - complete kdewebdev - cmake - complete kdegraphics - cmake - complete
Thanks to everyone
Baho Utot wrote:
I have now successfully packaged the following for Arch Linux with the PKGBUILDs and some bash scripts for building this set. They will need to be built using a clean chroot see this link for explaination: https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_Clean_Chroo... The PKGBUILD script will show the dependencies for each package. I will moving on to the applications shortly, I need a little break ;)
That's understandable.
If anyone is interested i have placed the scripts here: git clone https://github.com/baho-utot/trinity.git until they can be incorperated into the tde-packaging repo.
Is there a way to browse the scripts?
# # Dependencies # qt3 - autotools - complete tqtinterface - cmake - complete arts - cmake - complete dbus-tqt - cmake - complete dbus-1-tqt - cmake - complete # # Desktop # kdelibs - cmake - complete kdebase - cmake - complete kdebindings - not needed - not needed kdeaccessibility- autotools - complete kdeutils - autotools - complete kdemultimedia - autotools - complete kdeadmin - autotools - complete kdeartwork - autotools - complete kdegames - autotools - complete kdetoys - autotools - complete kdeedu - autotools - complete kdepim - cmake - complete kdesdk - autotools - complete kdeaddons - autotools - complete kdevelop - cmake - complete kdewebdev - cmake - complete kdegraphics - cmake - complete
Are you going to do the i18n files? AFAIK, there is still a make/make install needed for kdebindings.
Where are the source files for the i18n files and kdewebdev? Thanks.
-- Bruce
On Tuesday 27 December 2011 10:15:24 pm Bruce Dubbs wrote:
Baho Utot wrote:
[putolin]
If anyone is interested i have placed the scripts here: git clone https://github.com/baho-utot/trinity.git until they can be incorperated into the tde-packaging repo.
Is there a way to browse the scripts?
I think this link will get you there
github.com/baho-utot/trinity
I can browse it with chromium and konqueror. Under the applications section none of those builds work now as those are wip everything else should work. I have scripted this build so as to do a few "seds" and it will build version 14 when it comes out.
I think you could create a wrapper script and source the PKGBUILD from there and it shoud work for you. Something like this I think might work for you. I think you would only need to set the srcdir and pkgdir variables before you source the PKGBUILD script
wrapper.sh #!/bin/bash srcdir=${1} pkgdir=${2} tar xf ${1}/$pkgname-$pkgver.tar.gz source PKGBUILD
Then cd to the directory with the build script and <path to wrapper>/wrapper.sh <path to source ie where the tarball was extracted> <path to where you want the files installed>
Are you going to do the i18n files? AFAIK, there is still a make/make install needed for kdebindings.
I want to package all the version 3.5 13 files. So I have a complete set. I hope it works out that way.
I didn't do kdebindings as it wasn't needed to build the rest ( I think). I will look at the kdebindings soon.
Where are the source files for the i18n files and kdewebdev?
I got all the sources tarballs from the 3.5.13-complete.tar tarball off the trinitydesktop site.
Go here and it is at the bottom: http://mirror.ets.kth.se/trinity/releases/3.5.13/downloads.html Click "All core and non-core modules list above"
The i18n will be in the 3.5.13-monolithic.tar.gz file so if you would like those you will also need to fetch it from the same link but click "Complete core and non-core source tree"
There is also a link "All non-core modules listed above" but I don't know what it contains as I didn't download that one.
You can also get the source like this:
pkgname=tdebase pkgver=3.5.13 mksource() { git clone http://scm.trinitydesktop.org/scm/git/$%7Bpkgname%7D pushd ${pkgname} git submodule init git submodule update git checkout v3.5.13 popd tar -cvJf ${pkgname}-${pkgver}.tar.xz ${pkgname}/* rm -fr ${pkgname} }
I don't know if the i18n files can be fetched from git like above.
Hope this helps
Baho Utot wrote:
On Tuesday 27 December 2011 10:15:24 pm Bruce Dubbs wrote:
Baho Utot wrote:
[putolin]
If anyone is interested i have placed the scripts here: git clone https://github.com/baho-utot/trinity.git until they can be incorperated into the tde-packaging repo.
Is there a way to browse the scripts?
I think this link will get you there
github.com/baho-utot/trinity
I can browse it with chromium and konqueror. Under the applications section none of those builds work now as those are wip everything else should work. I have scripted this build so as to do a few "seds" and it will build version 14 when it comes out.
I think you could create a wrapper script and source the PKGBUILD from there and it shoud work for you. Something like this I think might work for you. I think you would only need to set the srcdir and pkgdir variables before you source the PKGBUILD script
wrapper.sh #!/bin/bash srcdir=${1} pkgdir=${2} tar xf ${1}/$pkgname-$pkgver.tar.gz source PKGBUILD
Then cd to the directory with the build script and <path to wrapper>/wrapper.sh <path to source ie where the tarball was extracted> <path to where you want the files installed>
OK, that's helpful info. My users will want something a little different as they do not always have all the dependencies installed, but what you've done will help me sort that out.
I got all the sources tarballs from the 3.5.13-complete.tar tarball off the trinitydesktop site.
Go here and it is at the bottom: http://mirror.ets.kth.se/trinity/releases/3.5.13/downloads.html Click "All core and non-core modules list above"
The i18n will be in the 3.5.13-monolithic.tar.gz file so if you would like those you will also need to fetch it from the same link but click "Complete core and non-core source tree"
Oh good. The is a good site now. Downloading now.
There is also a link "All non-core modules listed above" but I don't know what it contains as I didn't download that one.
You can also get the source like this:
pkgname=tdebase pkgver=3.5.13 mksource() { git clone http://scm.trinitydesktop.org/scm/git/$%7Bpkgname%7D pushd ${pkgname} git submodule init git submodule update git checkout v3.5.13 popd tar -cvJf ${pkgname}-${pkgver}.tar.xz ${pkgname}/* rm -fr ${pkgname} }
I don't know if the i18n files can be fetched from git like above.
Hope this helps
Yes it does. Thanks you.
-- Bruce
On Wednesday 28 December 2011 02:02:27 pm Bruce Dubbs wrote:
Baho Utot wrote:
On Tuesday 27 December 2011 10:15:24 pm Bruce Dubbs wrote:
Baho Utot wrote:
[putolin]
Then cd to the directory with the build script and <path to wrapper>/wrapper.sh <path to source ie where the tarball was extracted> <path to where you want the files installed>
OK, that's helpful info. My users will want something a little different as they do not always have all the dependencies installed, but what you've done will help me sort that out.
Yes the bugger is in all the dependencies, not that I have found all of them. I think with your help we can get a pretty good handle on the dependencies.
What I have got is a build that works for me. It may need additional work as I don't use a lot of what is in KDE3/Trinity. After you publish TDE to BLFS I'll have a look at it and add to my build system.
Actually I forgot in the wrapper script you would also have to have build and package; wrapper.sh #!/bin/bash srcdir=${1} pkgdir=${2} tar xf ${1}/$pkgname-$pkgver.tar.gz source PKGBUILD build package
I got all the sources tarballs from the 3.5.13-complete.tar tarball off the trinitydesktop site.
Go here and it is at the bottom: http://mirror.ets.kth.se/trinity/releases/3.5.13/downloads.html Click "All core and non-core modules list above"
The i18n will be in the 3.5.13-monolithic.tar.gz file so if you would like those you will also need to fetch it from the same link but click "Complete core and non-core source tree"
Oh good. The is a good site now. Downloading now.
Baho Utot wrote:
Yes the bugger is in all the dependencies, not that I have found all of them. I think with your help we can get a pretty good handle on the dependencies.
What I have got is a build that works for me. It may need additional work as I don't use a lot of what is in KDE3/Trinity. After you publish TDE to BLFS I'll have a look at it and add to my build system.
Take a look now. I wouldn't think that what is there from KDE3 would be that different from Trinity. I'm about halfway through the update.
-- Bruce
-
Baho Utot -
Bruce Dubbs