>I thought we had all of that renaming business behind us. I was
>surprised to find so many unintended renames still out there.
>There
>probably are more. I will not be suprised if one or two affect
>usability, but the remainder basically only affect readability and
>appearance. I wish we were done with them.
I am running a full build tonight. I'll find out if I was
overzealous with the renaming cleanup.
Darrell
>How to solve it? Fix in common/admin module would cause the update
>completely
>all other modules. This does not seem appropriate for this moment.
>Solve it
>stand alone in Tellico?
>
>Thank you for your feedback.
Updating Tellico for R14.0.0 is a priority? Perhaps wait until
R14.0.1/R14.1.0?
By the way, I'm in the middle of pushing a bunch of unintended TQ
renaming patches. I recall tellico being affected.
Darrell
Hi all,
in preparation patch to update Tellico from 1.3.2.1 to 1.3.6, I found that
DCOPIDLNG does not work. I was looking for that in common/admin module is to
find TQTDCOPIDLNG in condition by the variable $trinity14ornewer, but this
variable in that range is not valid. TQTDCOPIDLNG for this reason remains
empty and use DCOPIDLNG then causes FTBFS.
How to solve it? Fix in common/admin module would cause the update completely
all other modules. This does not seem appropriate for this moment. Solve it
stand alone in Tellico?
Thank you for your feedback.
--
Slavek
All,
Testing kthesaurus functionality, I built the optional dependency with latest
WordNet-3.0 and then updated library database files to the latest 3.1 version of
the files. (3.0 is last release - 3.1 is a database only update). It works very
well and adds a whole new aspect of thesaurus functionality. It provides the
synonymous words in sentence context. Here a two screenshots of both the generic
kthesaurus output and the WordNet extension:
http://www.3111skyline.com/dl/dt/trinity/ss/koffice-kthesaurus.jpghttp://www.3111skyline.com/dl/dt/trinity/ss/koffice-kthesaurus-wordnet.jpg
If you want to include WordNet in your build, you will need 'tk' as a
dependency, then you will need:
WordNet-3.0:
http://wordnetcode.princeton.edu/3.0/WordNet-3.0.tar.bz2
3.1 Database Update:
http://wordnetcode.princeton.edu/wn3.1.dict.tar.gz
Then build with:
./configure --prefix=/usr --mandir=/usr/share/man
## change screwy location of dictionary and other dirs:
sed 's:#define DEFAULTPATH "/usr/dict":#define DEFAULTPATH
"/usr/share/wordnet/dict":' -i config.h
sed 's:"/usr/local/WordNet-3.0/lib/wnres":"/usr/share/wordnet/wnres":' -i src/wnb
make CFLAGS="$CFLAGS -DUSE_INTERP_RESULT"
The continue with packaging (moving default dirs to logical place and update to
3.1 database files):
make DESTDIR=$pkgdir install
mv $pkgdir/usr/doc $pkgdir/usr/share/wordnet
mv $pkgdir/usr/lib/wnres $pkgdir/usr/share/wordnet/wnres
rm -fr $pkgdir/usr/include/tk
# Replace dictionary files
cp -a $srcdir/dict/ $pkgdir/usr/share/wordnet/dict
rm -fr $pkgdir/usr/dict
install -D -m644 $srcdir/wordnet.desktop
$pkgdir/usr/share/applications/wordnet.desktop
install -D -m644 $srcdir/wordnet.png $pkgdir/usr/share/pixmaps/wordnet.png
install -D -m644 COPYING $pkgdir/usr/share/licenses/$pkgname/COPYING
Works well. About a 12M package and 50M install.
--
David C. Rankin, J.D.,P.E.
>No, not at all. That must be controlled by the:
>
>export TDEDIR=/opt/trinity
>export TDEDIRS=$TDEDIR
I have that in all build scripts.
>That's is all I can think of. Can you think of any extra tests on
>my end that might disclose anything else?
Nope. I suppose that is how things will remain until somebody
tackles the bug report. I'm guessing there are presumptions
associated with the problem that are not obvious to blockheads.
Like me.
Darrell
Hi all,
within commit c926c513 been moved "all" Amarok icons from the folder
share/apps/amarok/icons to common folder share/icons. This has resulted in a
file conflict between other packages. In my case, I noticed conflict on
babelfish.png from amarok × konq-plugins (tdeaddons).
With this commit was moved to a common folder some icons with too general
names, which are very potential source of conflicts. For example:
collection.png, dynamic.png, mini_dock.png, random.png, visualizations.png.
How to solve it? Rename icons to have the prefix amarok_ (many other icons is
named like this)? Move the icons back and into common folder move only
necessary icons? Any other ideas?
Note: It seems that it will be necessary to check whether not exists some
another conflicts. Michele, please could you check conflicts using your local
repository of binary packages?
Thanks
--
Slavek
All,
Sourcing various environment variables is straightforward with
distros that use /etc/profile.d. How are those variables sourced in
distros that do not use /etc/profile.d? In both commmand line
logins and graphical?
Darrell
>> I can't get the packages to build. There is no such directory as
>> $(KDE_INCLUDES)/tde. Or $(KDE_INCLUDES)/trinity.
>
>Huh 'KDE_INCLUDES', 'KDE_INCLUDES/trinity' ??
>
>I couldn't find those either, but 'TDE_...' can be found.
Do you have /opt/trinity/include/tde in your build environment?
Darrell