FYI
Here is an updated status on my progress on building TDE for the Arch liubx distro. I am going to place all the pkgbuild files into a git repository. I will be starting on some of the apps shortly.
Is there a place on the trinity website where the 3.5.13 indivual source tarballs are stored?
I need this so I can place the url into the build scripts so that the package management system that builds source on arch linux can download by package as needed.
qt3 - complete 2011-12-22 tqtinterface - complete 2011-12-22 arts - complete 2011-12-22 dbus-tqt - complete 2011-12-22 dbus-1-tqt - complete 2011-12-22 kdelibs - complete 2011-12-22 kdebase - complete 2011-12-22 kdebindings - not needed kdeaccessibility- complete 2011-12-23 kdeutils - complete 2011-12-23 kdemultimedia - complete 2011-12-23 kdenetwork - barfed kdeadmin - complete 2011-12-23 kdeartwork - complete 2011-12-23 kdegames - complete 2011-12-23 kdetoys - complete 2011-12-23 kdeedu - complete 2011-12-23 kdegraphics - barfed kdevelop - complete 2011-12-23 kdeaddons - complete 2011-12-23 kdewebdev - kdepim - complete 2011-12-23 kdesdk - complete 2011-12-23
Thanks
Baho Utot wrote:
FYI
Here is an updated status on my progress on building TDE for the Arch liubx distro. I am going to place all the pkgbuild files into a git repository. I will be starting on some of the apps shortly.
Is there a place on the trinity website where the 3.5.13 indivual source tarballs are stored?
I need this so I can place the url into the build scripts so that the package management system that builds source on arch linux can download by package as needed.
qt3 - complete 2011-12-22 tqtinterface - complete 2011-12-22 arts - complete 2011-12-22 dbus-tqt - complete 2011-12-22 dbus-1-tqt - complete 2011-12-22 kdelibs - complete 2011-12-22 kdebase - complete 2011-12-22 kdebindings - not needed kdeaccessibility- complete 2011-12-23 kdeutils - complete 2011-12-23 kdemultimedia - complete 2011-12-23 kdenetwork - barfed kdeadmin - complete 2011-12-23 kdeartwork - complete 2011-12-23 kdegames - complete 2011-12-23 kdetoys - complete 2011-12-23 kdeedu - complete 2011-12-23 kdegraphics - barfed kdevelop - complete 2011-12-23 kdeaddons - complete 2011-12-23 kdewebdev - kdepim - complete 2011-12-23 kdesdk - complete 2011-12-23
You can use http://anduin.linuxfromscratch.org/sources/trinity/
-- Bruce
On Friday 23 December 2011 02:21:18 pm Bruce Dubbs wrote:
[putolin]
You can use http://anduin.linuxfromscratch.org/sources/trinity/
-- Bruce
Thanks Bruce
Baho,
I think again we are duplicating our work. Me and Pawel have had PKGBUILDs available for some time.
Calvin On Dec 23, 2011 2:21 PM, "Bruce Dubbs" bruce.dubbs@gmail.com wrote:
Baho Utot wrote:
FYI
Here is an updated status on my progress on building TDE for the Arch liubx distro. I am going to place all the pkgbuild files into a git repository. I will be starting on some of the apps shortly.
Is there a place on the trinity website where the 3.5.13 indivual source tarballs are stored?
I need this so I can place the url into the build scripts so that the package management system that builds source on arch linux can download by package as needed.
qt3 - complete 2011-12-22 tqtinterface - complete 2011-12-22 arts - complete 2011-12-22 dbus-tqt - complete 2011-12-22 dbus-1-tqt - complete 2011-12-22 kdelibs - complete 2011-12-22 kdebase - complete 2011-12-22 kdebindings - not needed kdeaccessibility- complete 2011-12-23 kdeutils - complete 2011-12-23 kdemultimedia - complete 2011-12-23 kdenetwork - barfed kdeadmin - complete 2011-12-23 kdeartwork - complete 2011-12-23 kdegames - complete 2011-12-23 kdetoys - complete 2011-12-23 kdeedu - complete 2011-12-23 kdegraphics - barfed kdevelop - complete 2011-12-23 kdeaddons - complete 2011-12-23 kdewebdev - kdepim - complete 2011-12-23 kdesdk - complete 2011-12-23
You can use http://anduin.**linuxfromscratch.org/sources/**trinity/http://anduin.linuxfromscratch.org/sources/trinity/
-- Bruce
------------------------------**------------------------------**--------- To unsubscribe, e-mail: trinity-devel-unsubscribe@** lists.pearsoncomputing.nettrinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.** pearsoncomputing.net trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.** pearsoncomputing.net/ http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.** pearsoncomputing.net/mailing_**lists/#top-postinghttp://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Friday 23 December 2011 02:58:43 pm Calvin Morrison wrote:
Baho,
I think again we are duplicating our work. Me and Pawel have had PKGBUILDs available for some time.
Calvin
[putolin]
Have not seen them.
My pkgbuilds are very different from the ones in AUR.
I have TDE going into /usr. I have to fix a small issue with my qt3 so qt4 can be installed without error though.
On 23 December 2011 11:17, Baho Utot baho-utot@columbus.rr.com wrote:
On Friday 23 December 2011 02:58:43 pm Calvin Morrison wrote:
Baho,
I think again we are duplicating our work. Me and Pawel have had
PKGBUILDs
available for some time.
Calvin
[putolin]
Have not seen them.
My pkgbuilds are very different from the ones in AUR.
I have TDE going into /usr. I have to fix a small issue with my qt3 so qt4 can be installed without error though.
That's not a big difference - only a path. I don't see why we continue to duplicate our work. All of our sources so far are available in the Git repository.
Calvin
On Friday 23 December 2011 04:18:37 pm Calvin Morrison wrote:
On 23 December 2011 11:17, Baho Utot baho-utot@columbus.rr.com wrote:
On Friday 23 December 2011 02:58:43 pm Calvin Morrison wrote:
Baho,
I think again we are duplicating our work. Me and Pawel have had
PKGBUILDs
available for some time.
Calvin
[putolin]
Have not seen them.
My pkgbuilds are very different from the ones in AUR.
I have TDE going into /usr. I have to fix a small issue with my qt3 so qt4 can be installed without error though.
That's not a big difference - only a path. I don't see why we continue to duplicate our work. All of our sources so far are available in the Git repository.
Calvin
Didn't see them.
Sorry I don't see my work as a duplication. I have developed my pkgbuilds to work with a fresh install of arch linux and to adhere and integrate into arch linux the way the arch developers have out lined in their package building guide. I also build in a clean chroot environment and namcap both the packages and the build scripts. The scripts I have are not completely without error according to namacp but they are really close. I have examined the scripts in AUR, they are not to my standards.
On 23 December 2011 16:25, Baho Utot baho-utot@columbus.rr.com wrote:
On Friday 23 December 2011 04:18:37 pm Calvin Morrison wrote:
On 23 December 2011 11:17, Baho Utot baho-utot@columbus.rr.com wrote:
On Friday 23 December 2011 02:58:43 pm Calvin Morrison wrote:
Baho,
I think again we are duplicating our work. Me and Pawel have had
PKGBUILDs
available for some time.
Calvin
[putolin]
Have not seen them.
My pkgbuilds are very different from the ones in AUR.
I have TDE going into /usr. I have to fix a small issue with my qt3 so qt4 can be installed without error though.
That's not a big difference - only a path. I don't see why we continue to duplicate our work. All of our sources so far are available in the Git repository.
Calvin
Didn't see them.
Sorry I don't see my work as a duplication.
Duplicate - 3. To make or perform again; repeat.
You are duplicating the work when you could be contributing.
I have developed my pkgbuilds to work with a fresh install of arch linux and to adhere and integrate into arch linux the way the arch developers have out lined in their package building guide.
Wow thats awesome! why don't you contribute to the project by helping us? It seems ridiculous for you to be playing the part of Maverick here especially since I don't even really want to do the packaging. I'm just doing it because no one else has stepped up yet.
The Arch Way as far as I see it implies leaving everything upstream.
I also build in a clean chroot environment and namcap both the packages and the build scripts. The scripts I have are not completely without error according to namacp but they are really close. I have examined the scripts in AUR, they are not to my standards.
Doesn't everyone else do this? :-) I test our scripts not in a chroot, but a VM. Even cleaner.
namcap is a great utility which I have not utilized much. While examining the scripts in the AUR you didn't think to improve them or even bother to talk to us? Instead you went your own way? I don't mean to be harsh but this all seems very counter intuitive.
Instead of completely shrugging off the work we've put into in, why not work together? Everyone here is rooting for Trinity, and we are both arch users.
Calvin Morrison
On Friday 23 December 2011 04:42:07 pm Calvin Morrison wrote:
On 23 December 2011 16:25, Baho Utot baho-utot@columbus.rr.com wrote:
On Friday 23 December 2011 04:18:37 pm Calvin Morrison wrote:
On 23 December 2011 11:17, Baho Utot baho-utot@columbus.rr.com wrote:
On Friday 23 December 2011 02:58:43 pm Calvin Morrison wrote:
Baho,
I think again we are duplicating our work. Me and Pawel have had
PKGBUILDs
available for some time.
Calvin
[putolin]
Have not seen them.
My pkgbuilds are very different from the ones in AUR.
I have TDE going into /usr. I have to fix a small issue with my qt3 so qt4 can be installed without error though.
That's not a big difference - only a path. I don't see why we continue to duplicate our work. All of our sources so far are available in the Git repository.
Calvin
Didn't see them.
Sorry I don't see my work as a duplication.
Duplicate - 3. To make or perform again; repeat.
You are duplicating the work when you could be contributing.
I see it as an alternative.
I have developed my pkgbuilds to work with a fresh install of arch linux and to adhere and integrate into arch linux the way the arch developers have out lined in their package building guide.
Wow thats awesome! why don't you contribute to the project by helping us? It seems ridiculous for you to be playing the part of Maverick here especially since I don't even really want to do the packaging. I'm just doing it because no one else has stepped up yet.
It takes me a little longer to get things done as I am an old fart. What I would like to do is to get my pkbuilds into git so anyone can clone the repo and then fix, add to the work etc.
What has been missing as I see it is a place for a git repo so anyone can pull from it and make the builds better. I don't see that as being a maverick, to me you folks have abondoned me to my own accord.
I was willing to put from a git repo and contribute, but first I needed to learn how to package trinity and then learn git. I think I now have a solid trinty build "system" in place.
I am starting learning git right now.
The Arch Way as far as I see it implies leaving everything upstream.
Want to guess who's the upstream for trinity?
I also build in a clean chroot environment and namcap both the packages and the build scripts. The scripts I have are not completely without error according to namacp but they are really close. I have examined the scripts in AUR, they are not to my standards.
Doesn't everyone else do this? :-) I test our scripts not in a chroot, but a VM. Even cleaner.
Maybe so, but testing in a new install I think is better is even better.
namcap is a great utility which I have not utilized much. While examining the scripts in the AUR you didn't think to improve them or even bother to talk to us? Instead you went your own way? I don't mean to be harsh but this all seems very counter intuitive.
I had a bunch of problems with building the autotool packages, no one seemed to help except for Laurent Dard to which I am very very greatfull. From his help I found that the qt3 build was greatly borked. I have learned a lot with his help. I was able to correct my entire TDE build which was at that time horrible. BTW the AUR qt script has the same issues I had.
Instead of completely shrugging off the work we've put into in, why not work together? Everyone here is rooting for Trinity, and we are both arch users.
Some times for me I need to go it alone so I can learn. I am not as fast at this as others are.
<snip>
It takes me a little longer to get things done as I am an old fart. What I would like to do is to get my pkbuilds into git so anyone can clone the repo and then fix, add to the work etc.
What has been missing as I see it is a place for a git repo so anyone can pull from it and make the builds better. I don't see that as being a maverick, to me you folks have abondoned me to my own accord.
I was willing to put from a git repo and contribute, but first I needed to learn how to package trinity and then learn git. I think I now have a solid trinty build "system" in place.
I am starting learning git right now.
The TDE project provides GIT space to all distribution packagers. You can even maintain two separate copies of packaging files for a distribution if so desired; I leave all policy control within the distribution folder up to those who are actively working on that distribution.
Let me know if you need a GIT account.
Tim
On 23 December 2011 17:22, Timothy Pearson kb9vqf@pearsoncomputing.netwrote:
<snip> > It takes me a little longer to get things done as I am an old fart. What > I > would like to do is to get my pkbuilds into git so anyone can clone the > repo > and then fix, add to the work etc. > > What has been missing as I see it is a place for a git repo so anyone can > pull > from it and make the builds better. I don't see that as being a maverick, > to me you folks have abondoned me to my own accord. > > I was willing to put from a git repo and contribute, but first I needed to > learn how to package trinity and then learn git. I think I now have a > solid > trinty build "system" in place. > > I am starting learning git right now.
The TDE project provides GIT space to all distribution packagers. You can even maintain two separate copies of packaging files for a distribution if so desired; I leave all policy control within the distribution folder up to those who are actively working on that distribution.
Let me know if you need a GIT account.
Tim
We may as well keep a "Baho" folder for the builds contributed by Baho. Currently we have a 3.5.13 folder and a GIT (currently not working - waiting for git to settle out) folder. Another one won't hurt.
Calvin
[putolin]
The TDE project provides GIT space to all distribution packagers. You can even maintain two separate copies of packaging files for a distribution if so desired; I leave all policy control within the distribution folder up to those who are actively working on that distribution.
Let me know if you need a GIT account.
Tim
We may as well keep a "Baho" folder for the builds contributed by Baho. Currently we have a 3.5.13 folder and a GIT (currently not working - waiting for git to settle out) folder. Another one won't hurt.
Calvin
I am all for a single git arch pkgbuild directory. By having more than one only creates problems. If there is one place then every one can pull from there and create their own branch. Then you can merge back into the master and push to the public repo. At least that is what I get from the git community book. After I get access to a git repo I will see if it works that way.
On 23 December 2011 17:50, Baho Utot baho-utot@columbus.rr.com wrote:
[putolin]
The TDE project provides GIT space to all distribution packagers. You can even maintain two separate copies of packaging files for a distribution if so desired; I leave all policy control within the distribution folder up to those who are actively working on that distribution.
Let me know if you need a GIT account.
Tim
We may as well keep a "Baho" folder for the builds contributed by Baho. Currently we have a 3.5.13 folder and a GIT (currently not working - waiting for git to settle out) folder. Another one won't hurt.
Calvin
I am all for a single git arch pkgbuild directory. By having more than one only creates problems. If there is one place then every one can pull from there and create their own branch. Then you can merge back into the master and push to the public repo. At least that is what I get from the git community book. After I get access to a git repo I will see if it works that way.
sure let's stick to using branches :) that is more proper. Then we can merge onto to master branch as we go.
On Friday 23 December 2011 07:07:20 pm Calvin Morrison wrote:
On 23 December 2011 17:50, Baho Utot baho-utot@columbus.rr.com wrote:
[putolin]
The TDE project provides GIT space to all distribution packagers. You can even maintain two separate copies of packaging files for a distribution if so desired; I leave all policy control within the distribution folder up to those who are actively working on that distribution.
Let me know if you need a GIT account.
Tim
We may as well keep a "Baho" folder for the builds contributed by Baho. Currently we have a 3.5.13 folder and a GIT (currently not working - waiting for git to settle out) folder. Another one won't hurt.
Calvin
I am all for a single git arch pkgbuild directory. By having more than one only creates problems. If there is one place then every one can pull from there and create their own branch. Then you can merge back into the master and push to the public repo. At least that is what I get from the git community book. After I get access to a git repo I will see if it works that way.
sure let's stick to using branches :) that is more proper. Then we can merge onto to master branch as we go.
Ok I have git access now.
Is there a test area I can experiment with?
I setup an account on gitotious as a test but I can do anything with it;( all it does is hangup on me.
On 23 December 2011 19:26, Baho Utot baho-utot@columbus.rr.com wrote:
On Friday 23 December 2011 07:07:20 pm Calvin Morrison wrote:
On 23 December 2011 17:50, Baho Utot baho-utot@columbus.rr.com wrote:
[putolin]
The TDE project provides GIT space to all distribution packagers. You can even maintain two separate copies of packaging files for a distribution if so desired; I leave all policy control within the distribution folder up to those who are actively working on that distribution.
Let me know if you need a GIT account.
Tim
We may as well keep a "Baho" folder for the builds contributed by
Baho.
Currently we have a 3.5.13 folder and a GIT (currently not working - waiting for git to settle out) folder. Another one won't hurt.
Calvin
I am all for a single git arch pkgbuild directory. By having more than one only creates problems. If there is one place then every one can
pull
from there and create their own branch. Then you can merge back into
the
master and push to the public repo. At least that is what I get from
the
git community book. After I get access to a git repo I will see if it works that way.
sure let's stick to using branches :) that is more proper. Then we can merge onto to master branch as we go.
Ok I have git access now.
Is there a test area I can experiment with?
I setup an account on gitotious as a test but I can do anything with it;( all it does is hangup on me.
As for external services - I recommend github 100%!
On Friday 23 December 2011 07:27:45 pm Calvin Morrison wrote:
On 23 December 2011 19:26, Baho Utot baho-utot@columbus.rr.com wrote:
On Friday 23 December 2011 07:07:20 pm Calvin Morrison wrote:
On 23 December 2011 17:50, Baho Utot baho-utot@columbus.rr.com wrote:
[putolin]
The TDE project provides GIT space to all distribution packagers. You can even maintain two separate copies of packaging files for a distribution if so desired; I leave all policy control within the distribution folder up to those who are actively working on that distribution.
Let me know if you need a GIT account.
Tim
We may as well keep a "Baho" folder for the builds contributed by
Baho.
Currently we have a 3.5.13 folder and a GIT (currently not working
- waiting for git to settle out) folder. Another one won't hurt.
Calvin
I am all for a single git arch pkgbuild directory. By having more than one only creates problems. If there is one place then every one can
pull
from there and create their own branch. Then you can merge back into
the
master and push to the public repo. At least that is what I get from
the
git community book. After I get access to a git repo I will see if it works that way.
sure let's stick to using branches :) that is more proper. Then we can merge onto to master branch as we go.
Ok I have git access now.
Is there a test area I can experiment with?
I setup an account on gitotious as a test but I can do anything with it;( all it does is hangup on me.
As for external services - I recommend github 100%!
I am just trying to get a git repo so test so I don't blowup the trinity repo while learning.
On 23 December 2011 19:32, Baho Utot baho-utot@columbus.rr.com wrote:
On Friday 23 December 2011 07:27:45 pm Calvin Morrison wrote:
On 23 December 2011 19:26, Baho Utot baho-utot@columbus.rr.com wrote:
On Friday 23 December 2011 07:07:20 pm Calvin Morrison wrote:
On 23 December 2011 17:50, Baho Utot baho-utot@columbus.rr.com
wrote:
[putolin]
> The TDE project provides GIT space to all distribution
packagers.
> You can even maintain two separate copies of packaging files
for
> a distribution if so desired; I leave all policy control within > the distribution folder up to those who are actively working on > that distribution. > > Let me know if you need a GIT account. > > Tim
We may as well keep a "Baho" folder for the builds contributed by
Baho.
Currently we have a 3.5.13 folder and a GIT (currently not
working
- waiting for git to settle out) folder. Another one won't hurt.
Calvin
I am all for a single git arch pkgbuild directory. By having more than one only creates problems. If there is one place then every
one
can
pull
from there and create their own branch. Then you can merge back
into
the
master and push to the public repo. At least that is what I get
from
the
git community book. After I get access to a git repo I will see if it works that way.
sure let's stick to using branches :) that is more proper. Then we
can
merge onto to master branch as we go.
Ok I have git access now.
Is there a test area I can experiment with?
I setup an account on gitotious as a test but I can do anything with
it;(
all it does is hangup on me.
As for external services - I recommend github 100%!
I am just trying to get a git repo so test so I don't blowup the trinity repo while learning.
you can blow it up as much as you wont - just don't push the changes.
I suggest viewing these videos - they helped me understand using git a bit better
http://www.youtube.com/watch?v=74yphulj3uo http://www.youtube.com/watch?v=TCFZHxoMUdE&feature=related
Maybe that can help you understand the contexts and branches - it's pretty good
On Friday 23 December 2011 07:34:52 pm Calvin Morrison wrote:
On 23 December 2011 19:32, Baho Utot baho-utot@columbus.rr.com wrote:
On Friday 23 December 2011 07:27:45 pm Calvin Morrison wrote:
On 23 December 2011 19:26, Baho Utot baho-utot@columbus.rr.com wrote:
On Friday 23 December 2011 07:07:20 pm Calvin Morrison wrote:
On 23 December 2011 17:50, Baho Utot baho-utot@columbus.rr.com
wrote:
[putolin]
> > The TDE project provides GIT space to all distribution
packagers.
> > You can even maintain two separate copies of packaging files
for
> > a distribution if so desired; I leave all policy control > > within the distribution folder up to those who are actively > > working on that distribution. > > > > Let me know if you need a GIT account. > > > > Tim > > We may as well keep a "Baho" folder for the builds contributed > by
Baho.
> Currently we have a 3.5.13 folder and a GIT (currently not
working
> - waiting for git to settle out) folder. Another one won't > hurt. > > Calvin
I am all for a single git arch pkgbuild directory. By having more than one only creates problems. If there is one place then every
one
can
pull
from there and create their own branch. Then you can merge back
into
the
master and push to the public repo. At least that is what I get
from
the
git community book. After I get access to a git repo I will see if it works that way.
sure let's stick to using branches :) that is more proper. Then we
can
merge onto to master branch as we go.
Ok I have git access now.
Is there a test area I can experiment with?
I setup an account on gitotious as a test but I can do anything with
it;(
all it does is hangup on me.
As for external services - I recommend github 100%!
I am just trying to get a git repo so test so I don't blowup the trinity repo while learning.
you can blow it up as much as you wont - just don't push the changes.
I suggest viewing these videos - they helped me understand using git a bit better
http://www.youtube.com/watch?v=74yphulj3uo http://www.youtube.com/watch?v=TCFZHxoMUdE&feature=related
Maybe that can help you understand the contexts and branches - it's pretty good
OK, Thanks
I setup a github account I pushed my dependency subdirectory there Here is the url if you want to have a look. git@github.com:baho-utot/trinity.git
Now to begin work on the trinty git repo is the following coreect?
I have cloned the trinity repo with the pkgbuilds
Now I need to do this......
branch the repo with
git checkout -b wip
bend, break, fold and mutilate
then to merge the changes etc into the master
git merge wip
then git branch -d wip
Is this correct?
On Friday 23 December 2011 05:22:04 pm Timothy Pearson wrote:
<snip>
It takes me a little longer to get things done as I am an old fart. What I would like to do is to get my pkbuilds into git so anyone can clone the repo and then fix, add to the work etc.
What has been missing as I see it is a place for a git repo so anyone can pull from it and make the builds better. I don't see that as being a maverick, to me you folks have abondoned me to my own accord.
I was willing to put from a git repo and contribute, but first I needed to learn how to package trinity and then learn git. I think I now have a solid trinty build "system" in place.
I am starting learning git right now.
The TDE project provides GIT space to all distribution packagers. You can even maintain two separate copies of packaging files for a distribution if so desired; I leave all policy control within the distribution folder up to those who are actively working on that distribution.
Let me know if you need a GIT account.
Tim
Ok please set that up, and relay the information back to me so I can see if I can get that to work.
I have developed my pkgbuilds to work with a fresh install of arch linux and to adhere and integrate into arch linux the way the arch developers have out lined in their package building guide.
Wow thats awesome! why don't you contribute to the project by helping us? It seems ridiculous for you to be playing the part of Maverick here especially since I don't even really want to do the packaging. I'm just doing it because no one else has stepped up yet.
The Arch Way as far as I see it implies leaving everything upstream.
PKGBULDs I worte were wrote in new fresh Arch install and tested on 2 different VM's (one for i686, one for x86) and then tested on my laptop (fresh Arch install here too).
You are duplicating the work when you could be contributing.
+1
I see it as an alternative.
-1 Is there really that lot of difference between our PKGBUILDs and Yours?
On 12/24/2011 08:58 AM, L0ner sh4dou wrote:
I have developed my pkgbuilds to work with a fresh install of arch linux and to adhere and integrate into arch linux the way the arch developers have out lined in their package building guide.
Wow thats awesome! why don't you contribute to the project by helping us? It seems ridiculous for you to be playing the part of Maverick here especially since I don't even really want to do the packaging. I'm just doing it because no one else has stepped up yet.
The Arch Way as far as I see it implies leaving everything upstream.
PKGBULDs I worte were wrote in new fresh Arch install and tested on 2 different VM's (one for i686, one for x86) and then tested on my laptop (fresh Arch install here too).
You are duplicating the work when you could be contributing.
+1
I see it as an alternative.
-1 Is there really that lot of difference between our PKGBUILDs and Yours?
If in the follow there are spelling/grammar issues, spare me please as I have only a limited education.
Yes.
The PKGBUILD that I have done conform to the Arch linux packaging standards set by of course arch devs.
It is my opinion that if the scripts are not done in a manner as outlined in the package build document (on their site), the devs at arch linux will reject the pkgbuild scripts. I would like to see them included in the arch linux extra or community package repos. So quality counts in my opinion.
The qt3 build you have does have some broken-ness to it as well. I started with that PKGBUILD which led me down a path of horror. With Laurent Dard help I was able to fix the broken-ness and I now have a solid build set.
Upon looking at the Arch build repo you don't have a full set. It appears to me you are stuck at the autotool build packages as was I until Laurent help. I now have the following complete and working qt3, tqtinterface, arts, dbus-tqt, dbus-1-tqt, kdelibs, kdebase, kdebindings, kdeaccessibility, kdeutils, kdemultimedia, kdenetwork, deadmin, kdeartwork, kdegames, kdetoys, kdeedu, kdegraphics, kdevelop, kdeaddons, kdewebdev, kdepim and kdesdk. I need to do some cleanup work on my scripts and then I am on to the apps. I know they are working and good as I use them on my desktop machine and even at the present state of trinity not being complete it satisfies my needs. Even with the outstanding bugs in need of patches. Good job to the trinity devs, Thank you.
I am also adding a mksource function so that I can pull from the source git repo on trinitydesktop.org. I also need to complete my work with qt3 so it will install and work along with qt4, I have just a few files that are givin pacman a problem. I think it will be a non issue.
I have planned out my repo to match the source repo by having three sub directories called dependencies desktop and applications. I would like to see the trinity arch pkgbuild repo to move to something like that. The way the repo is now is very confusing to me.
Where are we going to start?
How many people are in the trinity arch linux developers/packagers?
What are the guide lines for the repo and how the pkgbuild scripts conform to ?
How to best incorporate my work into the repo?
The repo needs to be put in an order that makes sense so people that want to contribute can and all the 3.5.13 packages need to have PKGBUILD scripts.
I see your post as trying to start a dick size war so lets not do that and start being productive. I take your post as counter productive. Is this us against them here or what?
If you really don't want my help just say so, cancel my login to the git repo and I will go back to doing my own thing and putting my work on github, Just say so and I am gone. It's really not that hard for me and it's all good for me. I can help or I can leave it is up to you folks.
My work is presently here: https://github.com/baho-utot/trinity. You can clone those and put them here if you like.
2011/12/24 Baho Utot baho-utot@columbus.rr.com:
On 12/24/2011 08:58 AM, L0ner sh4dou wrote:
I have developed my pkgbuilds to work with a fresh install of arch linux and to adhere and integrate into arch linux the way the arch developers have out lined in their package building guide.
Wow thats awesome! why don't you contribute to the project by helping us? It seems ridiculous for you to be playing the part of Maverick here especially since I don't even really want to do the packaging. I'm just doing it because no one else has stepped up yet.
The Arch Way as far as I see it implies leaving everything upstream.
PKGBULDs I worte were wrote in new fresh Arch install and tested on 2 different VM's (one for i686, one for x86) and then tested on my laptop (fresh Arch install here too).
You are duplicating the work when you could be contributing.
+1
I see it as an alternative.
-1 Is there really that lot of difference between our PKGBUILDs and Yours?
If in the follow there are spelling/grammar issues, spare me please as I have only a limited education.
Yes.
The PKGBUILD that I have done conform to the Arch linux packaging standards set by of course arch devs.
I read the articles on the wiki and tried to keep close to the standards defined there. Please remember that those PKGBUILDs are still in some kind work-in progress state, since I'm generally new to writing them.
It is my opinion that if the scripts are not done in a manner as outlined in the package build document (on their site), the devs at arch linux will reject the pkgbuild scripts. I would like to see them included in the arch linux extra or community package repos. So quality counts in my opinion.
+1
The qt3 build you have does have some broken-ness to it as well. I started with that PKGBUILD which led me down a path of horror. With Laurent Dard help I was able to fix the broken-ness and I now have a solid build set.
qt3 wasn't done by me. I concentrated on adding new PKGBUILDs that we yet didn't have.
Upon looking at the Arch build repo you don't have a full set. It appears to me you are stuck at the autotool build packages as was I until Laurent help. I now have the following complete and working qt3, tqtinterface, arts, dbus-tqt, dbus-1-tqt, kdelibs, kdebase, kdebindings, kdeaccessibility, kdeutils, kdemultimedia, kdenetwork, deadmin, kdeartwork, kdegames, kdetoys, kdeedu, kdegraphics, kdevelop, kdeaddons, kdewebdev, kdepim and kdesdk. I need to do some cleanup work on my scripts and then I am on to the apps.
I fixed autotools issues a cople of days ago (8). And atm we have full set too in our git. Currentely I'm working on split package PKGBUILD for i18n and I've begun on working on apps too.
I know they are working and good as I use them on my desktop machine and even at the present state of trinity not being complete it satisfies my needs. Even with the outstanding bugs in need of patches. Good job to the trinity devs, Thank you.
I am also adding a mksource function so that I can pull from the source git repo on trinitydesktop.org.
+1 I've been thinking aboit that, postponed it until the git move is complete, which whould be 1st January.
I also need to complete my work with qt3 so it will install and work along with qt4, I have just a few files that are givin pacman a problem. I think it will be a non issue.
I have planned out my repo to match the source repo by having three sub directories called dependencies desktop and applications. I would like to see the trinity arch pkgbuild repo to move to something like that. The way the repo is now is very confusing to me.
see: http://trinity.etherpad.trinitydesktop.org/32
Where are we going to start?
I presume You have access to our git. Check out tde-packaging and begin on correcting whatever is wrong in our PKGBUILDs? Correct our PKGBUILDs templates?
How many people are in the trinity arch linux developers/packagers?
Atm: Me and Calvin who is maintainer of the whole thing.
What are the guide lines for the repo and how the pkgbuild scripts conform to ?
ATM: there is http://trinity.etherpad.trinitydesktop.org/32
How to best incorporate my work into the repo?
The repo needs to be put in an order that makes sense so people that want to contribute can and all the 3.5.13 packages need to have PKGBUILD scripts.
We are working on this.
I see your post as trying to start a dick size war so lets not do that and start being productive. I take your post as counter productive. Is this us against them here or what?
And you are wrong. I don't know how you see my attempt to start a war by asking how are different yours PKGBUILDs from ours.
If you really don't want my help just say so, cancel my login to the git repo and I will go back to doing my own thing and putting my work on github, Just say so and I am gone. It's really not that hard for me and it's all good for me. I can help or I can leave it is up to you folks.
My work is presently here: https://github.com/baho-utot/trinity. You can clone those and put them here if you like.
On 12/24/2011 11:06 AM, L0ner sh4dou wrote:
am on to the apps. I fixed autotools issues a cople of days ago (8). And atm we have full set too in our git. Currentely I'm working on split package PKGBUILD for i18n and I've begun on working on apps too.
I don't see them in the repo I cloned
I have arts qt3 dbus-tqt dbus-1-tqt kdebase kdelibs pyqt3 and tqtinterface. As you see all the ones built with autotools are missing.
The problem on merging work is that I am placing the packages into /usr and you are using /opt.
I would like to use /usr.
2011/12/24 Baho Utot baho-utot@columbus.rr.com:
On 12/24/2011 11:06 AM, L0ner sh4dou wrote:
am on to the apps. I fixed autotools issues a cople of days ago (8). And atm we have full set too in our git. Currentely I'm working on split package PKGBUILD for i18n and I've begun on working on apps too.
I don't see them in the repo I cloned
http://git.trinitydesktop.org/cgit/tde-packaging/tree/arch/3.5.13/trinity-ex...
I have arts qt3 dbus-tqt dbus-1-tqt kdebase kdelibs pyqt3 and tqtinterface. As you see all the ones built with autotools are missing.
The problem on merging work is that I am placing the packages into /usr and you are using /opt.
I would like to use /usr.
We decided to follow the trinity wiki instructions, which state that trinity should be put in /opt. Try asking Tim for explanations why, since personally I don't really know/remember. I think that in the end it's up to the user where it should be put. You can modify this in our PKGBUILDs by changing the _prefix variable.
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On 12/24/2011 11:53 AM, L0ner sh4dou wrote:
2011/12/24 Baho Utotbaho-utot@columbus.rr.com:
On 12/24/2011 11:06 AM, L0ner sh4dou wrote:
am on to the apps. I fixed autotools issues a cople of days ago (8). And atm we have full set too in our git. Currentely I'm working on split package PKGBUILD for i18n and I've begun on working on apps too.
I don't see them in the repo I cloned
http://git.trinitydesktop.org/cgit/tde-packaging/tree/arch/3.5.13/trinity-ex...
I have arts qt3 dbus-tqt dbus-1-tqt kdebase kdelibs pyqt3 and tqtinterface. As you see all the ones built with autotools are missing.
The problem on merging work is that I am placing the packages into /usr and you are using /opt.
I would like to use /usr.
We decided to follow the trinity wiki instructions, which state that trinity should be put in /opt. Try asking Tim for explanations why, since personally I don't really know/remember. I think that in the end it's up to the user where it should be put. You can modify this in our PKGBUILDs by changing the _prefix variable.
Yes I know I started the _prefix business back when David was active. I removed it from my builds because it is somewhat a violation of arch packaging rules. I choose /usr because the arch devs want that and because namcap throws alot of noise if it is not so. Namcap is a very good tool to be using, lets one know how bad your script and package really is, plus it picks up on all the dependencies. Running TDE in /usr has worked well for me. We as packagers must ultimatilly decide where TDE goes, I just choose to bend to the wishes of the distribution I am working on. Makes it easiser for them to give a adfirmative answer to include TDE in their repos. TDE will be judged by the build scripts when it comes to be included, which I think it will if we do a good job at packaging and bug fixing.
2011/12/24 Baho Utot baho-utot@columbus.rr.com:
On 12/24/2011 11:53 AM, L0ner sh4dou wrote:
2011/12/24 Baho Utotbaho-utot@columbus.rr.com:
On 12/24/2011 11:06 AM, L0ner sh4dou wrote:
am on to the apps. I fixed autotools issues a cople of days ago (8). And atm we have full set too in our git. Currentely I'm working on split package PKGBUILD for i18n and I've begun on working on apps too.
I don't see them in the repo I cloned
http://git.trinitydesktop.org/cgit/tde-packaging/tree/arch/3.5.13/trinity-ex...
I have arts qt3 dbus-tqt dbus-1-tqt kdebase kdelibs pyqt3 and tqtinterface. As you see all the ones built with autotools are missing.
The problem on merging work is that I am placing the packages into /usr and you are using /opt.
I would like to use /usr.
We decided to follow the trinity wiki instructions, which state that trinity should be put in /opt. Try asking Tim for explanations why, since personally I don't really know/remember. I think that in the end it's up to the user where it should be put. You can modify this in our PKGBUILDs by changing the _prefix variable.
Yes I know I started the _prefix business back when David was active. I removed it from my builds because it is somewhat a violation of arch packaging rules. I choose /usr because the arch devs want that and because namcap throws alot of noise if it is not so.
Throws nothing for me... strange(?)
Namcap is a very good tool to be using, lets one know how bad your script and package really is, plus it picks up on all the dependencies.
I know, I use it to check the PKGBUILDs I created till now.
Running TDE in /usr has worked well for me. We as packagers must ultimatilly decide where TDE goes, I just choose to bend to the wishes of the distribution I am working on. Makes it easiser for them to give a adfirmative answer to include TDE in their repos. TDE will be judged by the build scripts when it comes to be included, which I think it will if we do a good job at packaging and bug fixing.
For changing actual prefix to /usr: I think we should ask Calvin what he thinks about it, since he is the maintainer.
On 12/24/2011 12:34 PM, L0ner sh4dou wrote:
2011/12/24 Baho Utotbaho-utot@columbus.rr.com:
On 12/24/2011 11:53 AM, L0ner sh4dou wrote:
2011/12/24 Baho Utotbaho-utot@columbus.rr.com:
On 12/24/2011 11:06 AM, L0ner sh4dou wrote:
am on to the apps. I fixed autotools issues a cople of days ago (8). And atm we have full set too in our git. Currentely I'm working on split package PKGBUILD for i18n and I've begun on working on apps too.
I don't see them in the repo I cloned
http://git.trinitydesktop.org/cgit/tde-packaging/tree/arch/3.5.13/trinity-ex...
I have arts qt3 dbus-tqt dbus-1-tqt kdebase kdelibs pyqt3 and tqtinterface. As you see all the ones built with autotools are missing.
The problem on merging work is that I am placing the packages into /usr and you are using /opt.
I would like to use /usr.
We decided to follow the trinity wiki instructions, which state that trinity should be put in /opt. Try asking Tim for explanations why, since personally I don't really know/remember. I think that in the end it's up to the user where it should be put. You can modify this in our PKGBUILDs by changing the _prefix variable.
Yes I know I started the _prefix business back when David was active. I removed it from my builds because it is somewhat a violation of arch packaging rules. I choose /usr because the arch devs want that and because namcap throws alot of noise if it is not so.
Throws nothing for me... strange(?)
Really you should be getting something like this for example:
kdelibs W: Description should not contain the package name. kdelibs W: Referenced library 'kalyptus' is an uninstalled dependency kdelibs W: Dependency 'sh' on your system is a testing release kdelibs W: Dependency 'qt3' on your system is a testing release kdelibs W: Directory (usr/share/locale/all_languages) is empty kdelibs W: Directory (usr/share/icons/hicolor) is empty kdelibs W: File (usr/lib/libkresources.la) is a libtool file kdelibs W: File (usr/lib/libkglib.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_kcookiejar.la) is a libtool file kdelibs W: File (usr/lib/libkspell2.la) is a libtool file kdelibs W: File (usr/lib/libkwalletbackend.la) is a libtool file kdelibs W: File (usr/lib/libconnectionmanager.la) is a libtool file kdelibs W: File (usr/lib/libkhtml.la) is a libtool file kdelibs W: File (usr/lib/libkio.la) is a libtool file kdelibs W: File (usr/lib/libkdeui.la) is a libtool file kdelibs W: File (usr/lib/libkdecore.la) is a libtool file kdelibs W: File (usr/lib/libkdefx.la) is a libtool file kdelibs W: File (usr/lib/libkutils.la) is a libtool file kdelibs W: File (usr/lib/libkdeprint.la) is a libtool file kdelibs W: File (usr/lib/libkimproxy.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_dcopserver.la) is a libtool file kdelibs W: File (usr/lib/libkdeprint_management.la) is a libtool file kdelibs W: File (usr/lib/libkdesasl.la) is a libtool file kdelibs W: File (usr/lib/libkrsync.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_kded.la) is a libtool file kdelibs W: File (usr/lib/libkabc_ldapkio.la) is a libtool file kdelibs W: File (usr/lib/libkabc.la) is a libtool file kdelibs W: File (usr/lib/libkmdi2.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_klauncher.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_kcmshell.la) is a libtool file kdelibs W: File (usr/lib/libkdnssd.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_kio_http_cache_cleaner.la) is a libtool file kdelibs W: File (usr/lib/libkmdi.la) is a libtool file kdelibs W: File (usr/lib/libkabc_file.la) is a libtool file kdelibs W: File (usr/lib/libkparts.la) is a libtool file kdelibs W: File (usr/lib/libkabc_dir.la) is a libtool file kdelibs W: File (usr/lib/libkspell.la) is a libtool file kdelibs W: File (usr/lib/libkatepartinterfaces.la) is a libtool file kdelibs W: File (usr/lib/libkntlm.la) is a libtool file kdelibs W: File (usr/lib/libvcard.la) is a libtool file kdelibs W: File (usr/lib/libkjava.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_kbuildsycoca.la) is a libtool file kdelibs W: File (usr/lib/libkrandr.la) is a libtool file kdelibs W: File (usr/lib/libkscript.la) is a libtool file kdelibs W: File (usr/lib/libartskde.la) is a libtool file kdelibs W: File (usr/lib/libnetworkstatus.la) is a libtool file kdelibs W: File (usr/lib/libDCOP.la) is a libtool file kdelibs W: File (usr/lib/libkdefakes.la) is a libtool file kdelibs W: File (usr/lib/libknewstuff.la) is a libtool file kdelibs W: File (usr/lib/libkabc_net.la) is a libtool file kdelibs W: File (usr/lib/libkmediaplayer.la) is a libtool file kdelibs W: File (usr/lib/libkmid.la) is a libtool file kdelibs W: File (usr/lib/libkdesu.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_kconf_update.la) is a libtool file kdelibs W: File (usr/lib/libkwalletclient.la) is a libtool file kdelibs W: File (usr/lib/libkscreensaver.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_kio_uiserver.la) is a libtool file kdelibs W: File (usr/lib/libkunittest.la) is a libtool file kdelibs W: File (usr/lib/libktexteditor.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_kaddprinterwizard.la) is a libtool file kdelibs W: File (usr/lib/libkjs.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_cupsdconf.la) is a libtool file kdelibs W: File (usr/lib/trinity/kio_file.la) is a libtool file kdelibs W: File (usr/lib/trinity/kdeprint_ext.la) is a libtool file kdelibs W: File (usr/lib/trinity/kspell_ispell.la) is a libtool file kdelibs W: File (usr/lib/trinity/kdeprint_tool_escputil.la) is a libtool file kdelibs W: File (usr/lib/trinity/ktexteditor_insertfile.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_jp2.la) is a libtool file kdelibs W: File (usr/lib/trinity/libkdeprint_management_module.la) is a libtool file kdelibs W: File (usr/lib/trinity/kio_http_cache_cleaner.la) is a libtool file kdelibs W: File (usr/lib/trinity/kabc_ldapkio.la) is a libtool file kdelibs W: File (usr/lib/trinity/knotify.la) is a libtool file kdelibs W: File (usr/lib/trinity/kdeprint_lpdunix.la) is a libtool file kdelibs W: File (usr/lib/trinity/libkcertpart.la) is a libtool file kdelibs W: File (usr/lib/trinity/kfileaudiopreview.la) is a libtool file kdelibs W: File (usr/lib/trinity/kded_proxyscout.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_tga.la) is a libtool file kdelibs W: File (usr/lib/trinity/kbzip2filter.la) is a libtool file kdelibs W: File (usr/lib/trinity/kded_kdetrayproxy.la) is a libtool file kdelibs W: File (usr/lib/trinity/kaddprinterwizard.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_hdr.la) is a libtool file kdelibs W: File (usr/lib/trinity/kded_kssld.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_psd.la) is a libtool file kdelibs W: File (usr/lib/trinity/klauncher.la) is a libtool file kdelibs W: File (usr/lib/trinity/kcmshell.la) is a libtool file kdelibs W: File (usr/lib/trinity/ktexteditor_isearch.la) is a libtool file kdelibs W: File (usr/lib/trinity/cupsdconf.la) is a libtool file kdelibs W: File (usr/lib/trinity/kded.la) is a libtool file kdelibs W: File (usr/lib/trinity/kio_iso.la) is a libtool file kdelibs W: File (usr/lib/trinity/kabc_dir.la) is a libtool file kdelibs W: File (usr/lib/trinity/kdeprint_rlpr.la) is a libtool file kdelibs W: File (usr/lib/trinity/kio_http.la) is a libtool file kdelibs W: File (usr/lib/trinity/libkatepart.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_tiff.la) is a libtool file kdelibs W: File (usr/lib/trinity/kstyle_plastik_config.la) is a libtool file kdelibs W: File (usr/lib/trinity/ktexteditor_docwordcompletion.la) is a libtool file kdelibs W: File (usr/lib/trinity/kabc_net.la) is a libtool file kdelibs W: File (usr/lib/trinity/dcopserver.la) is a libtool file kdelibs W: File (usr/lib/trinity/kjavaappletviewer.la) is a libtool file kdelibs W: File (usr/lib/trinity/kcm_kresources.la) is a libtool file kdelibs W: File (usr/lib/trinity/kspell_aspell.la) is a libtool file kdelibs W: File (usr/lib/trinity/kio_metainfo.la) is a libtool file kdelibs W: File (usr/lib/trinity/libshellscript.la) is a libtool file kdelibs W: File (usr/lib/trinity/ktexteditor_kdatatool.la) is a libtool file kdelibs W: File (usr/lib/trinity/kded_networkstatus.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_xview.la) is a libtool file kdelibs W: File (usr/lib/trinity/libkhtmlpart.la) is a libtool file kdelibs W: File (usr/lib/trinity/kabcformat_binary.la) is a libtool file kdelibs W: File (usr/lib/trinity/kio_ghelp.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_ico.la) is a libtool file kdelibs W: File (usr/lib/trinity/kabc_file.la) is a libtool file kdelibs W: File (usr/lib/trinity/kdeprint_cups.la) is a libtool file kdelibs W: File (usr/lib/trinity/kio_ftp.la) is a libtool file kdelibs W: File (usr/lib/trinity/kded_kwalletd.la) is a libtool file kdelibs W: File (usr/lib/trinity/kstyle_highcontrast_config.la) is a libtool file kdelibs W: File (usr/lib/trinity/kio_help.la) is a libtool file kdelibs W: File (usr/lib/trinity/kconf_update.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_rgb.la) is a libtool file kdelibs W: File (usr/lib/trinity/kded_kdeprintd.la) is a libtool file kdelibs W: File (usr/lib/trinity/kcookiejar.la) is a libtool file kdelibs W: File (usr/lib/trinity/khtmlimagepart.la) is a libtool file kdelibs W: File (usr/lib/trinity/kded_kcookiejar.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_xcf.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_exr.la) is a libtool file kdelibs W: File (usr/lib/trinity/kio_uiserver.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_eps.la) is a libtool file kdelibs W: File (usr/lib/trinity/kbuildsycoca.la) is a libtool file kdelibs W: File (usr/lib/trinity/kded_kpasswdserver.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_pcx.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_dds.la) is a libtool file kdelibs W: File (usr/lib/trinity/kgzipfilter.la) is a libtool file kdelibs W: File (usr/lib/trinity/kdeprint_lpr.la) is a libtool file kdelibs W: File (usr/lib/trinity/libkmultipart.la) is a libtool file kdelibs W: File (usr/lib/trinity/plugins/styles/kthemestyle.la) is a libtool file kdelibs W: File (usr/lib/trinity/plugins/styles/plastik.la) is a libtool file kdelibs W: File (usr/lib/trinity/plugins/styles/highcolor.la) is a libtool file kdelibs W: File (usr/lib/trinity/plugins/styles/highcontrast.la) is a libtool file kdelibs W: File (usr/lib/trinity/plugins/styles/asteroid.la) is a libtool file kdelibs W: File (usr/lib/trinity/plugins/styles/light.la) is a libtool file kdelibs W: File (usr/lib/trinity/plugins/styles/keramik.la) is a libtool file kdelibs W: File (usr/lib/trinity/plugins/designer/kdewidgets.la) is a libtool file kdelibs W: File (usr/bin/start_kdeinit) does not have the world readable bit set. kdelibs W: File (usr/bin/start_kdeinit) is setuid or setgid. kdelibs W: File (usr/bin/kpac_dhcp_helper) does not have the world readable bit set. kdelibs W: File (usr/bin/kpac_dhcp_helper) is setuid or setgid. kdelibs W: File (usr/bin/fileshareset) does not have the world readable bit set. kdelibs W: File (usr/bin/fileshareset) is setuid or setgid. kdelibs W: File (usr/bin/kgrantpty) does not have the world readable bit set. kdelibs W: File (usr/bin/kgrantpty) is setuid or setgid. kdelibs W: Dependency libtiff included but already satisfied kdelibs W: Dependency alsa-lib included but already satisfied kdelibs W: Dependency libcups included but already satisfied kdelibs W: Dependency libxml2 included but already satisfied kdelibs W: Dependency hicolor-icon-theme included but already satisfied
Plus all the ones for files being out of place, If I installed to /opt/.... this list would be twice as long.
For changing actual prefix to /usr: I think we should ask Calvin what he thinks about it, since he is the maintainer.
Yes, although we need to resolve this as quickly as possible though
2011/12/24 Baho Utot baho-utot@columbus.rr.com:
On 12/24/2011 12:34 PM, L0ner sh4dou wrote:
2011/12/24 Baho Utotbaho-utot@columbus.rr.com:
On 12/24/2011 11:53 AM, L0ner sh4dou wrote:
2011/12/24 Baho Utotbaho-utot@columbus.rr.com:
On 12/24/2011 11:06 AM, L0ner sh4dou wrote:
am on to the apps. I fixed autotools issues a cople of days ago (8). And atm we have full set too in our git. Currentely I'm working on split package PKGBUILD for i18n and I've begun on working on apps too.
I don't see them in the repo I cloned
http://git.trinitydesktop.org/cgit/tde-packaging/tree/arch/3.5.13/trinity-ex...
I have arts qt3 dbus-tqt dbus-1-tqt kdebase kdelibs pyqt3 and tqtinterface. As you see all the ones built with autotools are missing.
The problem on merging work is that I am placing the packages into /usr and you are using /opt.
I would like to use /usr.
We decided to follow the trinity wiki instructions, which state that trinity should be put in /opt. Try asking Tim for explanations why, since personally I don't really know/remember. I think that in the end it's up to the user where it should be put. You can modify this in our PKGBUILDs by changing the _prefix variable.
Yes I know I started the _prefix business back when David was active. I removed it from my builds because it is somewhat a violation of arch packaging rules. I choose /usr because the arch devs want that and because namcap throws alot of noise if it is not so.
Throws nothing for me... strange(?)
Really you should be getting something like this for example:
kdelibs W: Description should not contain the package name. kdelibs W: Referenced library 'kalyptus' is an uninstalled dependency kdelibs W: Dependency 'sh' on your system is a testing release kdelibs W: Dependency 'qt3' on your system is a testing release kdelibs W: Directory (usr/share/locale/all_languages) is empty kdelibs W: Directory (usr/share/icons/hicolor) is empty kdelibs W: File (usr/lib/libkresources.la) is a libtool file kdelibs W: File (usr/lib/libkglib.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_kcookiejar.la) is a libtool file kdelibs W: File (usr/lib/libkspell2.la) is a libtool file kdelibs W: File (usr/lib/libkwalletbackend.la) is a libtool file kdelibs W: File (usr/lib/libconnectionmanager.la) is a libtool file kdelibs W: File (usr/lib/libkhtml.la) is a libtool file kdelibs W: File (usr/lib/libkio.la) is a libtool file kdelibs W: File (usr/lib/libkdeui.la) is a libtool file kdelibs W: File (usr/lib/libkdecore.la) is a libtool file kdelibs W: File (usr/lib/libkdefx.la) is a libtool file kdelibs W: File (usr/lib/libkutils.la) is a libtool file kdelibs W: File (usr/lib/libkdeprint.la) is a libtool file kdelibs W: File (usr/lib/libkimproxy.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_dcopserver.la) is a libtool file kdelibs W: File (usr/lib/libkdeprint_management.la) is a libtool file kdelibs W: File (usr/lib/libkdesasl.la) is a libtool file kdelibs W: File (usr/lib/libkrsync.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_kded.la) is a libtool file kdelibs W: File (usr/lib/libkabc_ldapkio.la) is a libtool file kdelibs W: File (usr/lib/libkabc.la) is a libtool file kdelibs W: File (usr/lib/libkmdi2.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_klauncher.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_kcmshell.la) is a libtool file kdelibs W: File (usr/lib/libkdnssd.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_kio_http_cache_cleaner.la) is a libtool file kdelibs W: File (usr/lib/libkmdi.la) is a libtool file kdelibs W: File (usr/lib/libkabc_file.la) is a libtool file kdelibs W: File (usr/lib/libkparts.la) is a libtool file kdelibs W: File (usr/lib/libkabc_dir.la) is a libtool file kdelibs W: File (usr/lib/libkspell.la) is a libtool file kdelibs W: File (usr/lib/libkatepartinterfaces.la) is a libtool file kdelibs W: File (usr/lib/libkntlm.la) is a libtool file kdelibs W: File (usr/lib/libvcard.la) is a libtool file kdelibs W: File (usr/lib/libkjava.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_kbuildsycoca.la) is a libtool file kdelibs W: File (usr/lib/libkrandr.la) is a libtool file kdelibs W: File (usr/lib/libkscript.la) is a libtool file kdelibs W: File (usr/lib/libartskde.la) is a libtool file kdelibs W: File (usr/lib/libnetworkstatus.la) is a libtool file kdelibs W: File (usr/lib/libDCOP.la) is a libtool file kdelibs W: File (usr/lib/libkdefakes.la) is a libtool file kdelibs W: File (usr/lib/libknewstuff.la) is a libtool file kdelibs W: File (usr/lib/libkabc_net.la) is a libtool file kdelibs W: File (usr/lib/libkmediaplayer.la) is a libtool file kdelibs W: File (usr/lib/libkmid.la) is a libtool file kdelibs W: File (usr/lib/libkdesu.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_kconf_update.la) is a libtool file kdelibs W: File (usr/lib/libkwalletclient.la) is a libtool file kdelibs W: File (usr/lib/libkscreensaver.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_kio_uiserver.la) is a libtool file kdelibs W: File (usr/lib/libkunittest.la) is a libtool file kdelibs W: File (usr/lib/libktexteditor.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_kaddprinterwizard.la) is a libtool file kdelibs W: File (usr/lib/libkjs.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_cupsdconf.la) is a libtool file kdelibs W: File (usr/lib/trinity/kio_file.la) is a libtool file kdelibs W: File (usr/lib/trinity/kdeprint_ext.la) is a libtool file kdelibs W: File (usr/lib/trinity/kspell_ispell.la) is a libtool file kdelibs W: File (usr/lib/trinity/kdeprint_tool_escputil.la) is a libtool file kdelibs W: File (usr/lib/trinity/ktexteditor_insertfile.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_jp2.la) is a libtool file kdelibs W: File (usr/lib/trinity/libkdeprint_management_module.la) is a libtool file kdelibs W: File (usr/lib/trinity/kio_http_cache_cleaner.la) is a libtool file kdelibs W: File (usr/lib/trinity/kabc_ldapkio.la) is a libtool file kdelibs W: File (usr/lib/trinity/knotify.la) is a libtool file kdelibs W: File (usr/lib/trinity/kdeprint_lpdunix.la) is a libtool file kdelibs W: File (usr/lib/trinity/libkcertpart.la) is a libtool file kdelibs W: File (usr/lib/trinity/kfileaudiopreview.la) is a libtool file kdelibs W: File (usr/lib/trinity/kded_proxyscout.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_tga.la) is a libtool file kdelibs W: File (usr/lib/trinity/kbzip2filter.la) is a libtool file kdelibs W: File (usr/lib/trinity/kded_kdetrayproxy.la) is a libtool file kdelibs W: File (usr/lib/trinity/kaddprinterwizard.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_hdr.la) is a libtool file kdelibs W: File (usr/lib/trinity/kded_kssld.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_psd.la) is a libtool file kdelibs W: File (usr/lib/trinity/klauncher.la) is a libtool file kdelibs W: File (usr/lib/trinity/kcmshell.la) is a libtool file kdelibs W: File (usr/lib/trinity/ktexteditor_isearch.la) is a libtool file kdelibs W: File (usr/lib/trinity/cupsdconf.la) is a libtool file kdelibs W: File (usr/lib/trinity/kded.la) is a libtool file kdelibs W: File (usr/lib/trinity/kio_iso.la) is a libtool file kdelibs W: File (usr/lib/trinity/kabc_dir.la) is a libtool file kdelibs W: File (usr/lib/trinity/kdeprint_rlpr.la) is a libtool file kdelibs W: File (usr/lib/trinity/kio_http.la) is a libtool file kdelibs W: File (usr/lib/trinity/libkatepart.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_tiff.la) is a libtool file kdelibs W: File (usr/lib/trinity/kstyle_plastik_config.la) is a libtool file kdelibs W: File (usr/lib/trinity/ktexteditor_docwordcompletion.la) is a libtool file kdelibs W: File (usr/lib/trinity/kabc_net.la) is a libtool file kdelibs W: File (usr/lib/trinity/dcopserver.la) is a libtool file kdelibs W: File (usr/lib/trinity/kjavaappletviewer.la) is a libtool file kdelibs W: File (usr/lib/trinity/kcm_kresources.la) is a libtool file kdelibs W: File (usr/lib/trinity/kspell_aspell.la) is a libtool file kdelibs W: File (usr/lib/trinity/kio_metainfo.la) is a libtool file kdelibs W: File (usr/lib/trinity/libshellscript.la) is a libtool file kdelibs W: File (usr/lib/trinity/ktexteditor_kdatatool.la) is a libtool file kdelibs W: File (usr/lib/trinity/kded_networkstatus.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_xview.la) is a libtool file kdelibs W: File (usr/lib/trinity/libkhtmlpart.la) is a libtool file kdelibs W: File (usr/lib/trinity/kabcformat_binary.la) is a libtool file kdelibs W: File (usr/lib/trinity/kio_ghelp.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_ico.la) is a libtool file kdelibs W: File (usr/lib/trinity/kabc_file.la) is a libtool file kdelibs W: File (usr/lib/trinity/kdeprint_cups.la) is a libtool file kdelibs W: File (usr/lib/trinity/kio_ftp.la) is a libtool file kdelibs W: File (usr/lib/trinity/kded_kwalletd.la) is a libtool file kdelibs W: File (usr/lib/trinity/kstyle_highcontrast_config.la) is a libtool file kdelibs W: File (usr/lib/trinity/kio_help.la) is a libtool file kdelibs W: File (usr/lib/trinity/kconf_update.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_rgb.la) is a libtool file kdelibs W: File (usr/lib/trinity/kded_kdeprintd.la) is a libtool file kdelibs W: File (usr/lib/trinity/kcookiejar.la) is a libtool file kdelibs W: File (usr/lib/trinity/khtmlimagepart.la) is a libtool file kdelibs W: File (usr/lib/trinity/kded_kcookiejar.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_xcf.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_exr.la) is a libtool file kdelibs W: File (usr/lib/trinity/kio_uiserver.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_eps.la) is a libtool file kdelibs W: File (usr/lib/trinity/kbuildsycoca.la) is a libtool file kdelibs W: File (usr/lib/trinity/kded_kpasswdserver.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_pcx.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_dds.la) is a libtool file kdelibs W: File (usr/lib/trinity/kgzipfilter.la) is a libtool file kdelibs W: File (usr/lib/trinity/kdeprint_lpr.la) is a libtool file kdelibs W: File (usr/lib/trinity/libkmultipart.la) is a libtool file kdelibs W: File (usr/lib/trinity/plugins/styles/kthemestyle.la) is a libtool file kdelibs W: File (usr/lib/trinity/plugins/styles/plastik.la) is a libtool file kdelibs W: File (usr/lib/trinity/plugins/styles/highcolor.la) is a libtool file kdelibs W: File (usr/lib/trinity/plugins/styles/highcontrast.la) is a libtool file kdelibs W: File (usr/lib/trinity/plugins/styles/asteroid.la) is a libtool file kdelibs W: File (usr/lib/trinity/plugins/styles/light.la) is a libtool file kdelibs W: File (usr/lib/trinity/plugins/styles/keramik.la) is a libtool file kdelibs W: File (usr/lib/trinity/plugins/designer/kdewidgets.la) is a libtool file kdelibs W: File (usr/bin/start_kdeinit) does not have the world readable bit set. kdelibs W: File (usr/bin/start_kdeinit) is setuid or setgid. kdelibs W: File (usr/bin/kpac_dhcp_helper) does not have the world readable bit set. kdelibs W: File (usr/bin/kpac_dhcp_helper) is setuid or setgid. kdelibs W: File (usr/bin/fileshareset) does not have the world readable bit set. kdelibs W: File (usr/bin/fileshareset) is setuid or setgid. kdelibs W: File (usr/bin/kgrantpty) does not have the world readable bit set. kdelibs W: File (usr/bin/kgrantpty) is setuid or setgid. kdelibs W: Dependency libtiff included but already satisfied kdelibs W: Dependency alsa-lib included but already satisfied kdelibs W: Dependency libcups included but already satisfied kdelibs W: Dependency libxml2 included but already satisfied kdelibs W: Dependency hicolor-icon-theme included but already satisfied
Plus all the ones for files being out of place, If I installed to /opt/.... this list would be twice as long.
For changing actual prefix to /usr: I think we should ask Calvin what he thinks about it, since he is the maintainer.
Yes, although we need to resolve this as quickly as possible though
As soon as he shows up. Make it after xmas.
On 24 December 2011 12:46, Baho Utot baho-utot@columbus.rr.com wrote:
On 12/24/2011 12:34 PM, L0ner sh4dou wrote:
2011/12/24 Baho Utot<baho-utot@columbus.rr.com**>:
On 12/24/2011 11:53 AM, L0ner sh4dou wrote:
2011/12/24 Baho Utot<baho-utot@columbus.rr.com**>:
On 12/24/2011 11:06 AM, L0ner sh4dou wrote:
am on to the apps. I fixed autotools issues a cople of days ago (8). And atm we have full set too in our git. Currentely I'm working on split package PKGBUILD for i18n and I've begun on working on apps too.
I don't see them in the repo I cloned
http://git.trinitydesktop.org/**cgit/tde-packaging/tree/arch/** 3.5.13/trinity-extrashttp://git.trinitydesktop.org/cgit/tde-packaging/tree/arch/3.5.13/trinity-extras
I have arts qt3 dbus-tqt dbus-1-tqt kdebase kdelibs pyqt3 and tqtinterface. As you see all the ones built with autotools are missing.
The problem on merging work is that I am placing the packages into /usr and you are using /opt.
I would like to use /usr.
We decided to follow the trinity wiki instructions, which state that trinity should be put in /opt. Try asking Tim for explanations why, since personally I don't really know/remember. I think that in the end it's up to the user where it should be put. You can modify this in our PKGBUILDs by changing the _prefix variable.
Yes I know I started the _prefix business back when David was active.
I removed it from my builds because it is somewhat a violation of arch packaging rules. I choose /usr because the arch devs want that and because namcap throws alot of noise if it is not so.
Throws nothing for me... strange(?)
Really you should be getting something like this for example:
kdelibs W: Description should not contain the package name. kdelibs W: Referenced library 'kalyptus' is an uninstalled dependency kdelibs W: Dependency 'sh' on your system is a testing release kdelibs W: Dependency 'qt3' on your system is a testing release kdelibs W: Directory (usr/share/locale/all_**languages) is empty kdelibs W: Directory (usr/share/icons/hicolor) is empty kdelibs W: File (usr/lib/libkresources.la) is a libtool file kdelibs W: File (usr/lib/libkglib.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_**kcookiejar.lahttp://libkdeinit_kcookiejar.la) is a libtool file kdelibs W: File (usr/lib/libkspell2.la) is a libtool file kdelibs W: File (usr/lib/libkwalletbackend.la) is a libtool file kdelibs W: File (usr/lib/libconnectionmanager.**lahttp://libconnectionmanager.la) is a libtool file kdelibs W: File (usr/lib/libkhtml.la) is a libtool file kdelibs W: File (usr/lib/libkio.la) is a libtool file kdelibs W: File (usr/lib/libkdeui.la) is a libtool file kdelibs W: File (usr/lib/libkdecore.la) is a libtool file kdelibs W: File (usr/lib/libkdefx.la) is a libtool file kdelibs W: File (usr/lib/libkutils.la) is a libtool file kdelibs W: File (usr/lib/libkdeprint.la) is a libtool file kdelibs W: File (usr/lib/libkimproxy.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_**dcopserver.lahttp://libkdeinit_dcopserver.la) is a libtool file kdelibs W: File (usr/lib/libkdeprint_**management.lahttp://libkdeprint_management.la) is a libtool file kdelibs W: File (usr/lib/libkdesasl.la) is a libtool file kdelibs W: File (usr/lib/libkrsync.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_kded.la) is a libtool file kdelibs W: File (usr/lib/libkabc_ldapkio.la) is a libtool file kdelibs W: File (usr/lib/libkabc.la) is a libtool file kdelibs W: File (usr/lib/libkmdi2.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_klauncher.**lahttp://libkdeinit_klauncher.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_kcmshell.**lahttp://libkdeinit_kcmshell.la) is a libtool file kdelibs W: File (usr/lib/libkdnssd.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_kio_http_**cache_cleaner.lahttp://libkdeinit_kio_http_cache_cleaner.la) is a libtool file kdelibs W: File (usr/lib/libkmdi.la) is a libtool file kdelibs W: File (usr/lib/libkabc_file.la) is a libtool file kdelibs W: File (usr/lib/libkparts.la) is a libtool file kdelibs W: File (usr/lib/libkabc_dir.la) is a libtool file kdelibs W: File (usr/lib/libkspell.la) is a libtool file kdelibs W: File (usr/lib/libkatepartinterfaces**.lahttp://libkatepartinterfaces.la) is a libtool file kdelibs W: File (usr/lib/libkntlm.la) is a libtool file kdelibs W: File (usr/lib/libvcard.la) is a libtool file kdelibs W: File (usr/lib/libkjava.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_**kbuildsycoca.lahttp://libkdeinit_kbuildsycoca.la) is a libtool file kdelibs W: File (usr/lib/libkrandr.la) is a libtool file kdelibs W: File (usr/lib/libkscript.la) is a libtool file kdelibs W: File (usr/lib/libartskde.la) is a libtool file kdelibs W: File (usr/lib/libnetworkstatus.la) is a libtool file kdelibs W: File (usr/lib/libDCOP.la) is a libtool file kdelibs W: File (usr/lib/libkdefakes.la) is a libtool file kdelibs W: File (usr/lib/libknewstuff.la) is a libtool file kdelibs W: File (usr/lib/libkabc_net.la) is a libtool file kdelibs W: File (usr/lib/libkmediaplayer.la) is a libtool file kdelibs W: File (usr/lib/libkmid.la) is a libtool file kdelibs W: File (usr/lib/libkdesu.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_kconf_**update.lahttp://libkdeinit_kconf_update.la) is a libtool file kdelibs W: File (usr/lib/libkwalletclient.la) is a libtool file kdelibs W: File (usr/lib/libkscreensaver.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_kio_**uiserver.lahttp://libkdeinit_kio_uiserver.la) is a libtool file kdelibs W: File (usr/lib/libkunittest.la) is a libtool file kdelibs W: File (usr/lib/libktexteditor.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_**kaddprinterwizard.lahttp://libkdeinit_kaddprinterwizard.la) is a libtool file kdelibs W: File (usr/lib/libkjs.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_cupsdconf.**lahttp://libkdeinit_cupsdconf.la) is a libtool file kdelibs W: File (usr/lib/trinity/kio_file.la) is a libtool file kdelibs W: File (usr/lib/trinity/kdeprint_ext.**lahttp://kdeprint_ext.la) is a libtool file kdelibs W: File (usr/lib/trinity/kspell_**ispell.lahttp://kspell_ispell.la) is a libtool file kdelibs W: File (usr/lib/trinity/kdeprint_**tool_escputil.lahttp://kdeprint_tool_escputil.la) is a libtool file kdelibs W: File (usr/lib/trinity/ktexteditor_**insertfile.lahttp://ktexteditor_insertfile.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_jp2.la) is a libtool file kdelibs W: File (usr/lib/trinity/libkdeprint_**management_module.lahttp://libkdeprint_management_module.la) is a libtool file kdelibs W: File (usr/lib/trinity/kio_http_**cache_cleaner.lahttp://kio_http_cache_cleaner.la) is a libtool file kdelibs W: File (usr/lib/trinity/kabc_ldapkio.**lahttp://kabc_ldapkio.la) is a libtool file kdelibs W: File (usr/lib/trinity/knotify.la) is a libtool file kdelibs W: File (usr/lib/trinity/kdeprint_**lpdunix.lahttp://kdeprint_lpdunix.la) is a libtool file kdelibs W: File (usr/lib/trinity/libkcertpart.**lahttp://libkcertpart.la) is a libtool file kdelibs W: File (usr/lib/trinity/kfileaudiopre**view.lahttp://kfileaudiopreview.la) is a libtool file kdelibs W: File (usr/lib/trinity/kded_**proxyscout.lahttp://kded_proxyscout.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_tga.la) is a libtool file kdelibs W: File (usr/lib/trinity/kbzip2filter.**lahttp://kbzip2filter.la) is a libtool file kdelibs W: File (usr/lib/trinity/kded_**kdetrayproxy.lahttp://kded_kdetrayproxy.la) is a libtool file kdelibs W: File (usr/lib/trinity/kaddprinterwi**zard.lahttp://kaddprinterwizard.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_hdr.la) is a libtool file kdelibs W: File (usr/lib/trinity/kded_kssld.la**) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_psd.la) is a libtool file kdelibs W: File (usr/lib/trinity/klauncher.la) is a libtool file kdelibs W: File (usr/lib/trinity/kcmshell.la) is a libtool file kdelibs W: File (usr/lib/trinity/ktexteditor_**isearch.lahttp://ktexteditor_isearch.la) is a libtool file kdelibs W: File (usr/lib/trinity/cupsdconf.la) is a libtool file kdelibs W: File (usr/lib/trinity/kded.la) is a libtool file kdelibs W: File (usr/lib/trinity/kio_iso.la) is a libtool file kdelibs W: File (usr/lib/trinity/kabc_dir.la) is a libtool file kdelibs W: File (usr/lib/trinity/kdeprint_**rlpr.lahttp://kdeprint_rlpr.la) is a libtool file kdelibs W: File (usr/lib/trinity/kio_http.la) is a libtool file kdelibs W: File (usr/lib/trinity/libkatepart.**la http://libkatepart.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_tiff.la) is a libtool file kdelibs W: File (usr/lib/trinity/kstyle_**plastik_config.lahttp://kstyle_plastik_config.la) is a libtool file kdelibs W: File (usr/lib/trinity/ktexteditor_**docwordcompletion.lahttp://ktexteditor_docwordcompletion.la) is a libtool file kdelibs W: File (usr/lib/trinity/kabc_net.la) is a libtool file kdelibs W: File (usr/lib/trinity/dcopserver.la**) is a libtool file kdelibs W: File (usr/lib/trinity/kjavaappletvi**ewer.lahttp://kjavaappletviewer.la) is a libtool file kdelibs W: File (usr/lib/trinity/kcm_**kresources.lahttp://kcm_kresources.la) is a libtool file kdelibs W: File (usr/lib/trinity/kspell_**aspell.lahttp://kspell_aspell.la) is a libtool file kdelibs W: File (usr/lib/trinity/kio_metainfo.**lahttp://kio_metainfo.la) is a libtool file kdelibs W: File (usr/lib/trinity/libshellscrip**t.lahttp://libshellscript.la) is a libtool file kdelibs W: File (usr/lib/trinity/ktexteditor_**kdatatool.lahttp://ktexteditor_kdatatool.la) is a libtool file kdelibs W: File (usr/lib/trinity/kded_**networkstatus.lahttp://kded_networkstatus.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_xview.la**) is a libtool file kdelibs W: File (usr/lib/trinity/libkhtmlpart.**lahttp://libkhtmlpart.la) is a libtool file kdelibs W: File (usr/lib/trinity/kabcformat_**binary.lahttp://kabcformat_binary.la) is a libtool file kdelibs W: File (usr/lib/trinity/kio_ghelp.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_ico.la) is a libtool file kdelibs W: File (usr/lib/trinity/kabc_file.la) is a libtool file kdelibs W: File (usr/lib/trinity/kdeprint_**cups.lahttp://kdeprint_cups.la) is a libtool file kdelibs W: File (usr/lib/trinity/kio_ftp.la) is a libtool file kdelibs W: File (usr/lib/trinity/kded_**kwalletd.lahttp://kded_kwalletd.la) is a libtool file kdelibs W: File (usr/lib/trinity/kstyle_**highcontrast_config.lahttp://kstyle_highcontrast_config.la) is a libtool file kdelibs W: File (usr/lib/trinity/kio_help.la) is a libtool file kdelibs W: File (usr/lib/trinity/kconf_update.**lahttp://kconf_update.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_rgb.la) is a libtool file kdelibs W: File (usr/lib/trinity/kded_**kdeprintd.lahttp://kded_kdeprintd.la) is a libtool file kdelibs W: File (usr/lib/trinity/kcookiejar.la**) is a libtool file kdelibs W: File (usr/lib/trinity/khtmlimagepar**t.lahttp://khtmlimagepart.la) is a libtool file kdelibs W: File (usr/lib/trinity/kded_**kcookiejar.lahttp://kded_kcookiejar.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_xcf.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_exr.la) is a libtool file kdelibs W: File (usr/lib/trinity/kio_uiserver.**lahttp://kio_uiserver.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_eps.la) is a libtool file kdelibs W: File (usr/lib/trinity/kbuildsycoca.**lahttp://kbuildsycoca.la) is a libtool file kdelibs W: File (usr/lib/trinity/kded_**kpasswdserver.lahttp://kded_kpasswdserver.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_pcx.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_dds.la) is a libtool file kdelibs W: File (usr/lib/trinity/kgzipfilter.**la http://kgzipfilter.la) is a libtool file kdelibs W: File (usr/lib/trinity/kdeprint_lpr.**lahttp://kdeprint_lpr.la) is a libtool file kdelibs W: File (usr/lib/trinity/libkmultipart**.lahttp://libkmultipart.la) is a libtool file kdelibs W: File (usr/lib/trinity/plugins/**styles/kthemestyle.la) is a libtool file kdelibs W: File (usr/lib/trinity/plugins/**styles/plastik.la) is a libtool file kdelibs W: File (usr/lib/trinity/plugins/**styles/highcolor.la) is a libtool file kdelibs W: File (usr/lib/trinity/plugins/**styles/highcontrast.la) is a libtool file kdelibs W: File (usr/lib/trinity/plugins/**styles/asteroid.la) is a libtool file kdelibs W: File (usr/lib/trinity/plugins/**styles/light.la) is a libtool file kdelibs W: File (usr/lib/trinity/plugins/**styles/keramik.la) is a libtool file kdelibs W: File (usr/lib/trinity/plugins/**designer/kdewidgets.la) is a libtool file kdelibs W: File (usr/bin/start_kdeinit) does not have the world readable bit set. kdelibs W: File (usr/bin/start_kdeinit) is setuid or setgid. kdelibs W: File (usr/bin/kpac_dhcp_helper) does not have the world readable bit set. kdelibs W: File (usr/bin/kpac_dhcp_helper) is setuid or setgid. kdelibs W: File (usr/bin/fileshareset) does not have the world readable bit set. kdelibs W: File (usr/bin/fileshareset) is setuid or setgid. kdelibs W: File (usr/bin/kgrantpty) does not have the world readable bit set. kdelibs W: File (usr/bin/kgrantpty) is setuid or setgid. kdelibs W: Dependency libtiff included but already satisfied kdelibs W: Dependency alsa-lib included but already satisfied kdelibs W: Dependency libcups included but already satisfied kdelibs W: Dependency libxml2 included but already satisfied kdelibs W: Dependency hicolor-icon-theme included but already satisfied
Plus all the ones for files being out of place, If I installed to /opt/.... this list would be twice as long.
For changing actual prefix to /usr: I think we should ask Calvin what he thinks about it, since he is the maintainer.
Yes, although we need to resolve this as quickly as possible though
I want to keep it in /opt to avoid issues with Qt4, kde4 and whatever hell they induce.
As for libtool issues, aren't we supposed to install the .la files? :x
I think our team is Me (Calvin) , Baho and Pawel (Loner). David is officially gone. I am also in contact with the kdemod3 repository and they are willing to take packages asap.
Calvin
2011/12/24 Calvin Morrison mutantturkey@gmail.com:
On 24 December 2011 12:46, Baho Utot baho-utot@columbus.rr.com wrote:
On 12/24/2011 12:34 PM, L0ner sh4dou wrote:
2011/12/24 Baho Utotbaho-utot@columbus.rr.com:
On 12/24/2011 11:53 AM, L0ner sh4dou wrote:
2011/12/24 Baho Utotbaho-utot@columbus.rr.com:
On 12/24/2011 11:06 AM, L0ner sh4dou wrote: > > am on to the apps. > I fixed autotools issues a cople of days ago (8). And atm we have > full > set too in our git. Currentely I'm working on split package PKGBUILD > for i18n and I've begun on working on apps too.
I don't see them in the repo I cloned
http://git.trinitydesktop.org/cgit/tde-packaging/tree/arch/3.5.13/trinity-ex...
I have arts qt3 dbus-tqt dbus-1-tqt kdebase kdelibs pyqt3 and tqtinterface. As you see all the ones built with autotools are missing.
The problem on merging work is that I am placing the packages into /usr and you are using /opt.
I would like to use /usr.
We decided to follow the trinity wiki instructions, which state that trinity should be put in /opt. Try asking Tim for explanations why, since personally I don't really know/remember. I think that in the end it's up to the user where it should be put. You can modify this in our PKGBUILDs by changing the _prefix variable.
Yes I know I started the _prefix business back when David was active. I removed it from my builds because it is somewhat a violation of arch packaging rules. I choose /usr because the arch devs want that and because namcap throws alot of noise if it is not so.
Throws nothing for me... strange(?)
Really you should be getting something like this for example:
kdelibs W: Description should not contain the package name. kdelibs W: Referenced library 'kalyptus' is an uninstalled dependency kdelibs W: Dependency 'sh' on your system is a testing release kdelibs W: Dependency 'qt3' on your system is a testing release kdelibs W: Directory (usr/share/locale/all_languages) is empty kdelibs W: Directory (usr/share/icons/hicolor) is empty kdelibs W: File (usr/lib/libkresources.la) is a libtool file kdelibs W: File (usr/lib/libkglib.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_kcookiejar.la) is a libtool file kdelibs W: File (usr/lib/libkspell2.la) is a libtool file kdelibs W: File (usr/lib/libkwalletbackend.la) is a libtool file kdelibs W: File (usr/lib/libconnectionmanager.la) is a libtool file kdelibs W: File (usr/lib/libkhtml.la) is a libtool file kdelibs W: File (usr/lib/libkio.la) is a libtool file kdelibs W: File (usr/lib/libkdeui.la) is a libtool file kdelibs W: File (usr/lib/libkdecore.la) is a libtool file kdelibs W: File (usr/lib/libkdefx.la) is a libtool file kdelibs W: File (usr/lib/libkutils.la) is a libtool file kdelibs W: File (usr/lib/libkdeprint.la) is a libtool file kdelibs W: File (usr/lib/libkimproxy.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_dcopserver.la) is a libtool file kdelibs W: File (usr/lib/libkdeprint_management.la) is a libtool file kdelibs W: File (usr/lib/libkdesasl.la) is a libtool file kdelibs W: File (usr/lib/libkrsync.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_kded.la) is a libtool file kdelibs W: File (usr/lib/libkabc_ldapkio.la) is a libtool file kdelibs W: File (usr/lib/libkabc.la) is a libtool file kdelibs W: File (usr/lib/libkmdi2.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_klauncher.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_kcmshell.la) is a libtool file kdelibs W: File (usr/lib/libkdnssd.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_kio_http_cache_cleaner.la) is a libtool file kdelibs W: File (usr/lib/libkmdi.la) is a libtool file kdelibs W: File (usr/lib/libkabc_file.la) is a libtool file kdelibs W: File (usr/lib/libkparts.la) is a libtool file kdelibs W: File (usr/lib/libkabc_dir.la) is a libtool file kdelibs W: File (usr/lib/libkspell.la) is a libtool file kdelibs W: File (usr/lib/libkatepartinterfaces.la) is a libtool file kdelibs W: File (usr/lib/libkntlm.la) is a libtool file kdelibs W: File (usr/lib/libvcard.la) is a libtool file kdelibs W: File (usr/lib/libkjava.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_kbuildsycoca.la) is a libtool file kdelibs W: File (usr/lib/libkrandr.la) is a libtool file kdelibs W: File (usr/lib/libkscript.la) is a libtool file kdelibs W: File (usr/lib/libartskde.la) is a libtool file kdelibs W: File (usr/lib/libnetworkstatus.la) is a libtool file kdelibs W: File (usr/lib/libDCOP.la) is a libtool file kdelibs W: File (usr/lib/libkdefakes.la) is a libtool file kdelibs W: File (usr/lib/libknewstuff.la) is a libtool file kdelibs W: File (usr/lib/libkabc_net.la) is a libtool file kdelibs W: File (usr/lib/libkmediaplayer.la) is a libtool file kdelibs W: File (usr/lib/libkmid.la) is a libtool file kdelibs W: File (usr/lib/libkdesu.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_kconf_update.la) is a libtool file kdelibs W: File (usr/lib/libkwalletclient.la) is a libtool file kdelibs W: File (usr/lib/libkscreensaver.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_kio_uiserver.la) is a libtool file kdelibs W: File (usr/lib/libkunittest.la) is a libtool file kdelibs W: File (usr/lib/libktexteditor.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_kaddprinterwizard.la) is a libtool file kdelibs W: File (usr/lib/libkjs.la) is a libtool file kdelibs W: File (usr/lib/libkdeinit_cupsdconf.la) is a libtool file kdelibs W: File (usr/lib/trinity/kio_file.la) is a libtool file kdelibs W: File (usr/lib/trinity/kdeprint_ext.la) is a libtool file kdelibs W: File (usr/lib/trinity/kspell_ispell.la) is a libtool file kdelibs W: File (usr/lib/trinity/kdeprint_tool_escputil.la) is a libtool file kdelibs W: File (usr/lib/trinity/ktexteditor_insertfile.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_jp2.la) is a libtool file kdelibs W: File (usr/lib/trinity/libkdeprint_management_module.la) is a libtool file kdelibs W: File (usr/lib/trinity/kio_http_cache_cleaner.la) is a libtool file kdelibs W: File (usr/lib/trinity/kabc_ldapkio.la) is a libtool file kdelibs W: File (usr/lib/trinity/knotify.la) is a libtool file kdelibs W: File (usr/lib/trinity/kdeprint_lpdunix.la) is a libtool file kdelibs W: File (usr/lib/trinity/libkcertpart.la) is a libtool file kdelibs W: File (usr/lib/trinity/kfileaudiopreview.la) is a libtool file kdelibs W: File (usr/lib/trinity/kded_proxyscout.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_tga.la) is a libtool file kdelibs W: File (usr/lib/trinity/kbzip2filter.la) is a libtool file kdelibs W: File (usr/lib/trinity/kded_kdetrayproxy.la) is a libtool file kdelibs W: File (usr/lib/trinity/kaddprinterwizard.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_hdr.la) is a libtool file kdelibs W: File (usr/lib/trinity/kded_kssld.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_psd.la) is a libtool file kdelibs W: File (usr/lib/trinity/klauncher.la) is a libtool file kdelibs W: File (usr/lib/trinity/kcmshell.la) is a libtool file kdelibs W: File (usr/lib/trinity/ktexteditor_isearch.la) is a libtool file kdelibs W: File (usr/lib/trinity/cupsdconf.la) is a libtool file kdelibs W: File (usr/lib/trinity/kded.la) is a libtool file kdelibs W: File (usr/lib/trinity/kio_iso.la) is a libtool file kdelibs W: File (usr/lib/trinity/kabc_dir.la) is a libtool file kdelibs W: File (usr/lib/trinity/kdeprint_rlpr.la) is a libtool file kdelibs W: File (usr/lib/trinity/kio_http.la) is a libtool file kdelibs W: File (usr/lib/trinity/libkatepart.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_tiff.la) is a libtool file kdelibs W: File (usr/lib/trinity/kstyle_plastik_config.la) is a libtool file kdelibs W: File (usr/lib/trinity/ktexteditor_docwordcompletion.la) is a libtool file kdelibs W: File (usr/lib/trinity/kabc_net.la) is a libtool file kdelibs W: File (usr/lib/trinity/dcopserver.la) is a libtool file kdelibs W: File (usr/lib/trinity/kjavaappletviewer.la) is a libtool file kdelibs W: File (usr/lib/trinity/kcm_kresources.la) is a libtool file kdelibs W: File (usr/lib/trinity/kspell_aspell.la) is a libtool file kdelibs W: File (usr/lib/trinity/kio_metainfo.la) is a libtool file kdelibs W: File (usr/lib/trinity/libshellscript.la) is a libtool file kdelibs W: File (usr/lib/trinity/ktexteditor_kdatatool.la) is a libtool file kdelibs W: File (usr/lib/trinity/kded_networkstatus.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_xview.la) is a libtool file kdelibs W: File (usr/lib/trinity/libkhtmlpart.la) is a libtool file kdelibs W: File (usr/lib/trinity/kabcformat_binary.la) is a libtool file kdelibs W: File (usr/lib/trinity/kio_ghelp.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_ico.la) is a libtool file kdelibs W: File (usr/lib/trinity/kabc_file.la) is a libtool file kdelibs W: File (usr/lib/trinity/kdeprint_cups.la) is a libtool file kdelibs W: File (usr/lib/trinity/kio_ftp.la) is a libtool file kdelibs W: File (usr/lib/trinity/kded_kwalletd.la) is a libtool file kdelibs W: File (usr/lib/trinity/kstyle_highcontrast_config.la) is a libtool file kdelibs W: File (usr/lib/trinity/kio_help.la) is a libtool file kdelibs W: File (usr/lib/trinity/kconf_update.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_rgb.la) is a libtool file kdelibs W: File (usr/lib/trinity/kded_kdeprintd.la) is a libtool file kdelibs W: File (usr/lib/trinity/kcookiejar.la) is a libtool file kdelibs W: File (usr/lib/trinity/khtmlimagepart.la) is a libtool file kdelibs W: File (usr/lib/trinity/kded_kcookiejar.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_xcf.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_exr.la) is a libtool file kdelibs W: File (usr/lib/trinity/kio_uiserver.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_eps.la) is a libtool file kdelibs W: File (usr/lib/trinity/kbuildsycoca.la) is a libtool file kdelibs W: File (usr/lib/trinity/kded_kpasswdserver.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_pcx.la) is a libtool file kdelibs W: File (usr/lib/trinity/kimg_dds.la) is a libtool file kdelibs W: File (usr/lib/trinity/kgzipfilter.la) is a libtool file kdelibs W: File (usr/lib/trinity/kdeprint_lpr.la) is a libtool file kdelibs W: File (usr/lib/trinity/libkmultipart.la) is a libtool file kdelibs W: File (usr/lib/trinity/plugins/styles/kthemestyle.la) is a libtool file kdelibs W: File (usr/lib/trinity/plugins/styles/plastik.la) is a libtool file kdelibs W: File (usr/lib/trinity/plugins/styles/highcolor.la) is a libtool file kdelibs W: File (usr/lib/trinity/plugins/styles/highcontrast.la) is a libtool file kdelibs W: File (usr/lib/trinity/plugins/styles/asteroid.la) is a libtool file kdelibs W: File (usr/lib/trinity/plugins/styles/light.la) is a libtool file kdelibs W: File (usr/lib/trinity/plugins/styles/keramik.la) is a libtool file kdelibs W: File (usr/lib/trinity/plugins/designer/kdewidgets.la) is a libtool file kdelibs W: File (usr/bin/start_kdeinit) does not have the world readable bit set. kdelibs W: File (usr/bin/start_kdeinit) is setuid or setgid. kdelibs W: File (usr/bin/kpac_dhcp_helper) does not have the world readable bit set. kdelibs W: File (usr/bin/kpac_dhcp_helper) is setuid or setgid. kdelibs W: File (usr/bin/fileshareset) does not have the world readable bit set. kdelibs W: File (usr/bin/fileshareset) is setuid or setgid. kdelibs W: File (usr/bin/kgrantpty) does not have the world readable bit set. kdelibs W: File (usr/bin/kgrantpty) is setuid or setgid. kdelibs W: Dependency libtiff included but already satisfied kdelibs W: Dependency alsa-lib included but already satisfied kdelibs W: Dependency libcups included but already satisfied kdelibs W: Dependency libxml2 included but already satisfied kdelibs W: Dependency hicolor-icon-theme included but already satisfied
Plus all the ones for files being out of place, If I installed to /opt/.... this list would be twice as long.
For changing actual prefix to /usr: I think we should ask Calvin what he thinks about it, since he is the maintainer.
Yes, although we need to resolve this as quickly as possible though
I want to keep it in /opt to avoid issues with Qt4, kde4 and whatever hell they induce.
True, since some kde4 apps have the same names as the trinity ones, having them in /usr would introduce chaos in the system.
As for libtool issues, aren't we supposed to install the .la files? :x
I think our team is Me (Calvin) , Baho and Pawel (Loner). David is officially gone. I am also in contact with the kdemod3 repository and they are willing to take packages asap.
Calvin
On 12/24/2011 02:51 PM, L0ner sh4dou wrote:
I want to keep it in /opt to avoid issues with Qt4, kde4 and whatever hell they induce. True, since some kde4 apps have the same names as the trinity ones, having them in /usr would introduce chaos in the system.
Not really pacman would just complain that the file already exists in the filesystem. Which is good info to know. Now there could be other issues to deal with as we'll see.
On 12/24/2011 02:41 PM, Calvin Morrison wrote:
For changing actual prefix to /usr: I think we should ask Calvin what he thinks about it, since he is the maintainer. Yes, although we need to resolve this as quickly as possible thoughI want to keep it in /opt to avoid issues with Qt4, kde4 and whatever hell they induce.
As for libtool issues, aren't we supposed to install the .la files? :x
I think our team is Me (Calvin) , Baho and Pawel (Loner). David is officially gone. I am also in contact with the kdemod3 repository and they are willing to take packages asap.
Calvin
I am not saying the libtool files are a problem, only included them to show a typical namcap run.
As far as the QT4 issues I have qt3 and qt4 almost sorted out I have the foolow issues
resolving dependencies... looking for inter-conflicts...
Targets (1): qt-4.7.4-3
Total Download Size: 0.00 MB Total Installed Size: 104.95 MB
Proceed with installation? [Y/n] checking package integrity... checking for file conflicts... error: failed to commit transaction (conflicting files) qt: /usr/bin/assistant exists in filesystem qt: /usr/bin/designer exists in filesystem qt: /usr/bin/linguist exists in filesystem qt: /usr/bin/lrelease exists in filesystem qt: /usr/bin/lupdate exists in filesystem qt: /usr/bin/moc exists in filesystem qt: /usr/bin/qmake exists in filesystem qt: /usr/bin/qtconfig exists in filesystem qt: /usr/bin/uic exists in filesystem qt: /usr/lib/qt/plugins/imageformats/libqjpeg.so exists in filesystem qt: /usr/lib/qt/plugins/imageformats/libqmng.so exists in filesystem qt: /usr/lib/qt/plugins/inputmethods/libqimsw-multi.so exists in filesystem qt: /usr/share/qt/mkspecs/default exists in filesystem qt: /usr/share/qt/mkspecs/linux-cxx/qmake.conf exists in filesystem qt: /usr/share/qt/mkspecs/linux-cxx/qplatformdefs.h exists in filesystem qt: /usr/share/qt/mkspecs/linux-ecc-64/qmake.conf exists in filesystem qt: /usr/share/qt/mkspecs/linux-ecc-64/qplatformdefs.h exists in filesystem qt: /usr/share/qt/mkspecs/linux-g++-32/qmake.conf exists in filesystem qt: /usr/share/qt/mkspecs/linux-g++-32/qplatformdefs.h exists in filesystem qt: /usr/share/qt/mkspecs/linux-g++-64/qmake.conf exists in filesystem qt: /usr/share/qt/mkspecs/linux-g++-64/qplatformdefs.h exists in filesystem qt: /usr/share/qt/mkspecs/linux-g++/qmake.conf exists in filesystem qt: /usr/share/qt/mkspecs/linux-g++/qplatformdefs.h exists in filesystem qt: /usr/share/qt/mkspecs/linux-icc/qmake.conf exists in filesystem qt: /usr/share/qt/mkspecs/linux-icc/qplatformdefs.h exists in filesystem qt: /usr/share/qt/mkspecs/linux-kcc/qmake.conf exists in filesystem qt: /usr/share/qt/mkspecs/linux-kcc/qplatformdefs.h exists in filesystem qt: /usr/share/qt/mkspecs/linux-pgcc/qmake.conf exists in filesystem qt: /usr/share/qt/mkspecs/linux-pgcc/qplatformdefs.h exists in filesystem qt: /usr/share/qt/phrasebooks/danish.qph exists in filesystem qt: /usr/share/qt/phrasebooks/dutch.qph exists in filesystem qt: /usr/share/qt/phrasebooks/finnish.qph exists in filesystem qt: /usr/share/qt/phrasebooks/french.qph exists in filesystem qt: /usr/share/qt/phrasebooks/german.qph exists in filesystem qt: /usr/share/qt/phrasebooks/italian.qph exists in filesystem qt: /usr/share/qt/phrasebooks/norwegian.qph exists in filesystem qt: /usr/share/qt/phrasebooks/russian.qph exists in filesystem qt: /usr/share/qt/phrasebooks/spanish.qph exists in filesystem qt: /usr/share/qt/phrasebooks/swedish.qph exists in filesystem Errors occurred, no packages were upgraded.
All of those issues will be going away after I get my bas build completed which is almost done.
If the build I am currently doing works thru then I am going to fix the above and test my build with everything in /usr with qt4 and kde4 installed.
-
Baho Utot -
Bruce Dubbs -
Calvin Morrison -
L0ner sh4dou -
Timothy Pearson