>> All,
>>
>> Debian fixed a bug with wv2 I need to patch/fix for tde. The
>bug was:
>>
>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707417
>>
>> How in the heck do you find out what debian did?
>
>Some problem with libxml was solved in KOffice - commit b6474af7.
Yes, but David asked how to find patches mentioned in Debian bug
reports. In the referenced bug report there are no links to an
actual patch. Only a textual reference the problem is resolved.
Darrell
>I would like to inspect source tree text strings for instances of
>KDE/kde rebranding issues and update to TDE/tde. Mostly in
>tooltips
>and What's This help strings. My challenge is being able to
>efficiently grep only those strings, which often in the sources
>are multiple lines.
>
>I would appreciate shell scripting advice to find such text
>strings.
Nobody knows?
Darrell
All -> Calvin,
While I plan on building R14 without hal, taking a look at the package on AUR,
hal still depends on eject. Eject now conflicts with util-linux, eject which
means we need to remove eject as a dependency. Do you plan on updating, or
should I just cannibalize it?
--
David C. Rankin, J.D.,P.E.
All,
With respect to the recent conversation about helping the Trinity
project, here is a list of apps that have no help handbooks:
kdevdesigner (tdevelop)
kstreamripper
tderadio
ksquirrel
ktorrent
kbarcode
kbarcode-single
kbarcode-editor
kbarcode-batch
kbibtex
kpalmdoc (kpilot)
dolphin
kiosktool
kvaio (kcontrol module)
thinkpad (kcontrol module)
kcmview1394 (kcontrol module)
display (kcontrol module)
kmobile (tdepim)
All of the apps have had no help handbook since the KDE3 days.
If you enjoy using one of those apps and want to help, please
consider writing something. You do not need to deal with docbook.
If you send me a text file I will massage the information into a
help handbook file.
The text need not be a novel. Sometimes a few paragraphs is
sufficient. For most handbooks, a description and highlighting the
main features is a nice start.
Thank you!
Darrell
All,
All packages that use automake and have subdirectories in the build tree may
fail to build with the release of automake 2.0. I am working on this for hal,
but I suspect other packages may be impacted. See:
https://bugs.freedesktop.org/show_bug.cgi?id=69874
--
David C. Rankin, J.D.,P.E.
>How much help does LibreOffice's own documentation offer? (For I
>have
>seen the ebuild, and it is an ugly beast with ~70 packages worth
>of
>dependencies. That's for the lightest configuration, which lacks
>cups
>support, any kind of scripting, and several other things. It
>would be
>much easier if we could just say, "follow this guide, but you'll
>need to
>pass this flag and this flag.")
As far as I can tell, something like the following is needed in the
build script:
====================
...
# Check for an installed Trinity and assume TQt.
# We need additional tests to ensure LO has been patched correctly.
TDEDIR=${TDEDIR:-""} # to avoid "TDEDIR: unbound variable"
if [ ! -z "$TDEDIR" ]; then
export TDEDIR="$TDEDIR"
export QTDIR="$QTDIR"
export QTINC="$QTDIR/include"
export QTLIB="$QTDIR/lib${LIBDIRSUFFIX}"
TDEOPTS="--enable-tde"
else
TDEOPTS="--disable-tde"
fi
...
./autogen.sh \
--prefix=/usr \
--docdir=/usr/doc/$PRGNAM-${LOVER}${VERSION}${PKG_SUBVER} \
--libdir=/usr/lib${LIBDIRSUFFIX} \
--sysconfdir=/etc \
--mandir=/usr/man \
...
${GITOPTS} \
${KDEOPTS} \
${TDEOPTS} \
...
====================
My build attempt failed when I tried to build the latest stable,
4.1.4. I filed bug report 1799 showing the failure messages.
http://bugs.trinitydesktop.org/show_bug.cgi?id=1799
Seems the expected directory and file location has changed from
previous versions of LO. My guess is we need to push an appropriate
patch upstream to the LO folks.
Darrell
>This is not a standard Debian / Ubuntu builds - it is Tim's builds
>on Trinity build-farm.
Luck you. :)
>By the way, in the Debian Wheezy is officially LibreOffice 3.5.4
>:) However, in wheezy-backports and Jessie is already 4.1.4.
I have 4.1.4 installed from a third party Slackware repo, but there
is no Trinity support. Asking to add that support would be a waste
of time as Trinity is not part of the "official" Slackware eco
system. All desktops not supported in the official releases must be
maintained by interested third parties.
This is why I filed the bug report and want to see a mini how-to
posted to the wiki. Those who are faced with compiling LO on their
own need all the support they can get.
Darrell
Calvin, (Archers)
Hal is failing at the beginning with a weird makefile error. Full error at:
http://www.3111skyline.com/dl/dt/tde/err/hal-makefile.err.txt
PKGBUILD is:
http://www.3111skyline.com/dl/dt/tde/err/PKGBUILD-hal
Basically the error looks like:
<snip>
parallel-tests: error: required file './test-driver' not found
parallel-tests: 'automake --add-missing' can install 'test-driver'
hald/linux/addons/Makefile.am:80: warning: source file '../../logger.c' is in a
subdirectory,
hald/linux/addons/Makefile.am:80: but option 'subdir-objects' is disabled
automake: warning: possible forward-incompatibility.
automake: At least a source file is in a subdirectory, but the 'subdir-objects'
automake: automake option hasn't been enabled. For now, the corresponding output
automake: object file(s) will be placed in the top-level directory. However,
automake: this behaviour will change in future Automake versions: they will
automake: unconditionally cause object files to be placed in the same subdirectory
automake: of the corresponding sources.
automake: You are advised to start using 'subdir-objects' option throughout your
automake: project, to avoid future incompatibilities.
hald/linux/addons/Makefile.am:80: warning: source file '../../util_helper.c' is
in a subdirectory,
hald/linux/addons/Makefile.am:80: but option 'subdir-objects' is disabled
hald/linux/addons/Makefile.am:84: warning: source file '../../logger.c' is in a
subdirectory,
hald/linux/addons/Makefile.am:84: but option 'subdir-objects' is disabled
hald/linux/addons/Makefile.am:84: warning: source file '../../util_helper.c' is
in a subdirectory,
hald/linux/addons/Makefile.am:84: but option 'subdir-objects' is disabled
hald/linux/addons/Makefile.am:62: warning: source file '../../logger.c' is in a
subdirectory,
hald/linux/addons/Makefile.am:62: but option 'subdir-objects' is disabled
hald/linux/addons/Makefile.am:62: warning: source file
'../../util_helper_priv.c' is in a subdirectory,
hald/linux/addons/Makefile.am:62: but option 'subdir-objects' is disabled
<snip>
hald/solaris/addons/Makefile.am:15: warning: source file '../../logger.c' is in
a subdirectory,
hald/solaris/addons/Makefile.am:15: but option 'subdir-objects' is disabled
hald/solaris/probing/Makefile.am:15: warning: source file '../../logger.c' is in
a subdirectory,
hald/solaris/probing/Makefile.am:15: but option 'subdir-objects' is disabled
hald/solaris/probing/Makefile.am:19: warning: source file '../../logger.c' is in
a subdirectory,
hald/solaris/probing/Makefile.am:19: but option 'subdir-objects' is disabled
partutil/Makefile.am:7: warning: source file '../hald/logger.c' is in a
subdirectory,
partutil/Makefile.am:7: but option 'subdir-objects' is disabled
policy/Makefile.am:27: warning: whitespace following trailing backslash
==> ERROR: A failure occurred in build().
So it blows up on policy/Makefile.am:27 after about 100 warnings. I'm not much
of a Makefile guy, so if you can check it, it would help.
--
David C. Rankin, J.D.,P.E.
>Python newb, and not really familiar with SCons as a build
>system, but my *guess* would be that you need to add:
>
>myenv.KDEinstall( 'KDEDOC', lang+'/'+destination,
>folder+'/index.docbook' )
>
>right after:
>
>myenv.KDEinstall( 'KDEDOC', lang+'/'+destination,
>folder+'/index.cache.bz2' )
>
>Make sure that the indentation of the two lines matches
>*exactly*, because leading whitespace is syntactically
>significant in Python.
I tried that. No luck. No build failures or complaints, but no
index.docbook in the package.
Darrell