tde-devels March 2019

devels@trinitydesktop.org

6 participants
5 discussions

tdelibs: Scanning dependencies of target check fails at dcop
by deloptes 03 Apr '19

03 Apr '19

Hi, I have below issue after updating to latest git and I was wondering how I can fix it. On the machine I build, I do not have GUI and dcop. In fact it is a chrooted environment. For now I disable the debian check target in the debian/rules file. Thank you in advance Scanning dependencies of target check make[4]: Leaving directory '/mnt/DEVELOPMENT/TDE/repo-master/tde/2_build/tdelibs/obj-x86_64-linux-gnu' /usr/bin/make -f dcop/tests/CMakeFiles/check.dir/build.make dcop/tests/CMakeFiles/check.dir/build make[4]: Entering directory '/mnt/DEVELOPMENT/TDE/repo-master/tde/2_build/tdelibs/obj-x86_64-linux-gnu' [100%] Running tests... /usr/bin/ctest Test project /mnt/DEVELOPMENT/TDE/repo-master/tde/2_build/tdelibs/obj-x86_64-linux-gnu Start 1: dcop/dcop-tests 1/40 Test #1: dcop/dcop-tests ...................................***Failed 1.05 sec Start 2: tdecore/tdeconfig_compiler/test1-cpp

3 5

[trinity-devel] need xrandr script to run as TDE 14.0.5 session starts in in Mageia
by Felix Miata 18 Mar '19

18 Mar '19

How can I get /etc/X11/wmsession.d/45TDE in Mageia 7b2 (urpmi upgraded from Mageia 6) to run my xrandr script as it starts? other distros call it from various places, but I can't find a place that works in Mageia 7. :~( TDM isn't working either, so I'm starting TDE with startx /opt/trinity/bin/starttde instead. Do I need something in /etc/alternatives to get TDM to work? If so, what? If not, then what? I'm only trying to follow up on a bug: https://bugs.mageia.org/show_bug.cgi?id=10457 -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/

1 0

tdemultimedia FTBFS
by deloptes 09 Mar '19

09 Mar '19

Hi, sorry to bother you again, but I do not know why I get this. I mean I understand why as shown below, but I do not understand where it is coming. This goes beyond my level of knowledge of cmake. Is it required to log a bug and how exactly - the trivial way would be in Gitea under tdemultimedia. Is this correct? dh_install: Cannot find (any matches for) "debian/tmp/opt/trinity/lib/libarts_mpeglib.so" (tried in "." and "debian/tmp") dh_install: tdemultimedia-trinity-dev missing files: debian/tmp/opt/trinity/lib/libarts_mpeglib.so dh_install: missing files, aborting /usr/share/cdbs/1/rules/debhelper.mk:233: recipe for target 'binary-install/tdemultimedia-trinity-dev' failed make: *** [binary-install/tdemultimedia-trinity-dev] Error 2 repo-master/tde/2_build/tdemultimedia/debian/tmp/opt/trinity/lib$ ls -al libarts_mpeglib* libarts_mpeglib-0.3.0.so -> libarts_mpeglib-0.3.0.so.0 libarts_mpeglib-0.3.0.so.0 -> libarts_mpeglib-0.3.0.so.0.0.3 libarts_mpeglib-0.3.0.so.0.0.3 libarts_mpeglib.la libarts_mpeglib.so.0 -> libarts_mpeglib-0.3.0.so.0.0 Seems libarts_mpeglib-0.3.0.so.0.0 is missing thanks in advance

2 2

Mail to François Andriot
by Slávek Banko 05 Mar '19

05 Mar '19

Hi, please have someone here any contact information on François which are functional? During preparation of R14.0.6 we need feedback if everything is OK on RPM distributions. But the contact information that I have is not working. Cheers -- Slávek

3 3

Preparation for work on translations
by Slávek Banko 01 Mar '19

01 Mar '19

Hi all, those of you who have been here for a long time might recall that when I joined the community I assumed that my tasks would be only two: backport patches to the stable TDE series and work on translation. Over time, it turned out that my tasks on the project would be bigger. However, work on translations is still a postponed task. Recently, I have devoted some time to the tasks that are essential to move us forward with the work on translations. Therefore, I would like to inform you about the results and related plans. I apologize for long email. 1. Unnecessary updates of POT files during package build I observed that during the DEB packages build, an attempt was made to update POT files. However, this step makes no sense. Bundling usually takes place in dedicated pure chroot. Therefore, the result of updating POT files would be discarded anyway. So this is unnecessary work. At the same time, the extractrc tool is used during the POT files update. But this tool is part of the tdesdk-scripts-trinity package. Therefore, when building other packages, it is usually not present. So updating POT files during building could not work well. That's why I already removed these unnecessary updates of POT files while building DEB packages. 2. Do we still need to use the old modified version of xgettext? I found out what the current status is and whether there are still reasons to use the old modified version of xgettext (kde-xgettext). Patches for the old version solve two things: a) adding a way to enter plural forms of strings b) adding a way to enter translation context The current versions of gexttext already have both of these options, but they seem to be implemented in a different way. Before we can start using standard xgettext in TDE, we will need to add support for a new way of plural forms of strings and translation contexts. So far, we need to continue using an old modified version of kde-xgettext. 3. Can modern gettext replace the extractrc tool? Modern versions of gettext can handle XML files. We use XML files for 'kcfg', 'rc' and 'ui'. Using ITS support in gettext, there is a way to define which texts are to be extracted for translations. I tested this option, but I encountered some problems: a) Tags are written in strings as html entities: < / > / &. After extraction using xgettext, are left in this form. But the extractrc tool convert them to the appropriate characters '<', '>', '&'. I did not find a way to do this with xgettext and ITS. b) XPath is used to determine which strings are to be extracted from XML files. Files 'kcfg' use their own XML namespace and I did not find a way how to enter XPath to work properly with ITS in xgettext. That's why I decided it was better to continue using the extractrc tool. 4. How do we create and update POT files? In order to provide strings for translation, we first need to create and update POT files. The best place for these files is right in the source code – in GIT. Therefore, these files need to be maintained independently of the building binaries. Therefore, it is obvious that for this task it is not a good time during the build binary packages, nor the usual use of Automake or CMake. Although the usual use of CMake with CMakeLists.txt for updating POT files is not a good choice, using CMake as such seems to be a good idea. CMake allows using the -P option to process a different file than the usual CMakeLists.txt. In this case, it does not create build folder, it does not create a cache - exactly as it suits us for our purpose. I decided to use the name CMakeL10n.txt. I have prepared the CMake module TDEL10n.cmake. This module provides functions for simplifing directories handling – function tde_add_l10n_subdirectory as the equivalent for add_subdirectory and function tde_auto_add_l10n_subdirectories as an equivalent for tde_auto_add_subdirectories. And above all, the tde_create_l10n_template macro that provides POT files generation. This macro provides some benefits that seemed useful: a) If resource files are processed – for example, *.ui, the work file "rc.cpp" is commonly used to save extracted strings for translation. This file is then processed by kde-xgettext. Links to the original location of strings in the resulting POT file then refer to this "rc.cpp", which is not very useful. The tde_create_l10n_template macro performs additional processing by replacing references to "rc.cpp" with references to the original resource files. Therefore, the POT file does not refer to a non-existent "rc.cpp" file, but to real locations in resource files. b) When a new POT file is generated, a comparison is made with the original POT file. If only the date of POT file generation is changed, the original POT file will be left unchanged. This prevents unnecessary POT file updates. This will allow to run a regular update of POT files without causing unnecessary commits. 5. What's next? For revisions and comments, I created a pull request containing a CMake module TDEL10n.cmake: https://mirror.git.trinitydesktop.org/gitea/TDE/tde-common-cmake/pulls/2 ...and pull requests with a demonstration of use CMakeL10n in two modules: https://mirror.git.trinitydesktop.org/gitea/TDE/abakus/pulls/1 https://mirror.git.trinitydesktop.org/gitea/TDE/tdebase/pulls/19 After testing, we will need to add CMakeL10n.txt to generate POT files in all other modules. Once we have automated updating of POT files, translation work can begin! 6. How can users work on translations? I will leave the answer to this question for later. Whoever was more attentive could have noticed in several earlier commits that "something is being prepared" :) Cheers -- Slávek

4 6

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels March 2019