29 Feb
2012
29 Feb
'12
4:16 a.m.
Tim,
If you already know this then never mind, but I needed to patch tdelibs and tdebase
against today's GIT updates for some remaining tde-config renaming. The patches are
here:
http://humanreadable.nfshost.com/trinity/patches/tdebase
Also two additional patches to build tdebase caused by recent tqt changes.
:)
Darrell
29 Feb
29 Feb
4:33 a.m.
New subject: [trinity-devel] More patches for today's GIT
Tim,
If you already know this then never mind, but I needed to patch tdelibs
and tdebase against today's GIT updates for some remaining tde-config
renaming. The patches are here:
http://humanreadable.nfshost.com/trinity/patches/tdebase
Also two additional patches to build tdebase caused by recent tqt changes.
:)
Darrell
Thanks for the patches. All of them are in GIT already, so I suspect that
you were unlucky enough to pull while the updates were being pushed. :-)
Just as an FYI tqt3 is undergoing changes to rename conflicting symbols
that were causing nasty crashes when tqt3 was used in a qt4 program. GIT
will probably fail to build against tqt3 for a day or two while I create
and push updates.
Thanks also for the docbook information; what I'll probably do for now is
just log which packages fail to build and let you know in one Email
message.
Tim
5:41 a.m.
New subject: [trinity-devel] More patches for today's GIT
Just as an FYI tqt3 is undergoing changes to rename
conflicting symbols that were causing nasty crashes when tqt3 was used in a qt4
program. GIT will probably fail to build against tqt3 for a day or two
while I create and push updates.
Let us know when that fire is dead. :)
Thanks also for the docbook information; what I'll
probably
do for now is just log which packages fail to build and let you know in
one Email message.
When you let us know the tqt glitches are gone I'll sync my local repository and
rebuild everything.
I solved the mystery how I missed pushing the tdevelop docbook patch --- the patch is
still sitting in my local tdevelop build directory. :)
Other than the aforementioned main/applications packages, that was the only main suite
package I missed pushing. There should not be problems with any other main suite
packages.
Until I get around to building all of the affected main/applications packages, should any
of those packages fail to build because of docbook problems, let me know and I'll push
the patch for that one package. Otherwise I'll keep those patches in my queue for
reasons I shared earlier. There are 39 affected packages. If I meet the beer truck head on
before pushing those patches, the fix is the same: change the DOCTYPE declaration to:
DocBook XML V4.2-Based Variant V1.1//EN
If you are building nightlies, I could gzip you the 39 patches and you could test in your
local repository. I simply don't yet have build scripts for all of the
main/applications packages. Or I could attach all of them in a gzip file to bug report
694. Your call. :)
Darrell
4711
days inactive
4711
days old
2 comments
2 participants
participants (2)
-
Darrell Anderson -
Timothy Pearson