tde-devels

devels@trinitydesktop.org

2 participants
3811 discussions

Do new git branches and tags (master->origin/master, etc.) change repo update calls?
by David C. Rankin 23 Dec '13

23 Dec '13

Tim, all, After a hiatus, I was updating my tde repos to see how horribly screwed I am attempting to build on Arch after their LSB and systemd changes. Pulling head I noted several new branch and tag names. I know what they are, but they look like they have added origin as a path component to 3.5.13-sru, etc.. Specifically, I saw: From http://scm.trinitydesktop.org/scm/git/tde + 8303efe...6fd6395 master -> origin/master (forced update) * [new branch] v3.5.13-sru -> origin/v3.5.13-sru So it looks like v3.5.13-sru is now origin/v3.5.13-sru. The question that brought up was "do I need to modify any of the scripts I use that update my local git repo to handle the 'origin/v3.5.13-sru' designation, or will the change be handled by the .gitmodule data? Additionally, there were new tags noted: ec1d9d9..9ec64b2 master -> origin/master 5ae82a0..169c39a v3.5.13-sru -> origin/v3.5.13-sru * [new tag] v3.5.13.1 -> v3.5.13.1 * [new tag] v3.5.13.2 -> v3.5.13.2 Same question, is there anything I would need to change in my existing checkout scripts such as: git submodule foreach --recursive "git checkout v3.5.13-sru" to reflect the new branch or tag designations? Like: git submodule foreach --recursive "git checkout origin/v3.5.13-sru" Also, if there are any new links or pointers for building 3.5.13 on bleeding edge distros like Arch, I would appreciate them as well. What is the state of HAL requirements? I presume it is still fully required in 3.5.13, but what about 14? I will be building 3.5.13, so I'll start by checking on the state of HAL in the Arch user repository. Thanks for any help you can give :) -- David C. Rankin, J.D.,P.E.

1 1

Re: [trinity-devel] How to insert a cmake variable into a *.desktop file
by Darrell Anderson 22 Dec '13

22 Dec '13

>Is it still actual? >Anyway... for future generations... the syntax is: > >Exec=@CMAKE_VARIABLE@ > >The desktop file is supposed to have ".cmake" extension. >In CMakeLists.txt use configure_file() statement. > >You can use e.g. tdebase/kdesktop/kdesktop.desktop.cmake as an >example... Thank you. As Slavek mentioned, I did learn how to do this. The challenge now is remembering. :) Darrell

1 0

Re: [trinity-devel] Etherpad font sizes
by Darrell Anderson 22 Dec '13

22 Dec '13

>I assume that the scale will help to Darrell, and there is no need >to change >the default font size. By the way, I sometimes adjusts to 85%. You must have a very large monitor. I have a 19" wide screen. Between the newly discovered magnifier option and browser fonts, I now have something --- acceptable. I notice the past many years an obsession by software and web site developers to use the smallest damn fonts possible. I presume the real problem is people using TVs for computer monitors and never testing anything on a standard desktop monitor. I notice the etherpad does not remember my magnification setting. Is there a way to preserve that? Darrell

1 0

Latest upstream package support for R14.0.0
by Darrell Anderson 22 Dec '13

22 Dec '13

All, What are the latest versions of various upstream packages that Trinity supports and compiles? Packages such as gcc, glibc, automake, cmake, libpng, cups, ffmpeg, etc. I am asking because I am updating the R14 press release draft. The more recent the list the better. Thank you! :-) Darrell

2 1

Etherpad font sizes
by Darrell Anderson 22 Dec '13

22 Dec '13

All, Is there anything I or we can do to increase the font sizes in etherpad? I'm not talking about hitting the browser page size button a bazillion times to completely distort the whole page. The fonts sizes are just too damn small. Thanks. Darrell

3 2

How to insert a cmake variable into a *.desktop file
by Darrell Anderson 22 Dec '13

22 Dec '13

All, I want to create a patch that modifies two *.desktop files during compile time. What is the correct syntax to use for the cmake variable in the *.desktop files? For example: Exec=%CMAKE_VARIABLE% Thanks. :-) Darrell

3 2

Re: [trinity-devel] tdelibs FTBFS: cmake 2.8.12: INTERFACE_LINK_LIBRARIES vs. LINK_INTERFACE_LIBRARIES
by Darrell Anderson 22 Dec '13

22 Dec '13

>Ok... I'll add both my patches there too... I suppose the further >discussion will take place there... Good idea because all of this is way over my head. :) Darrell

1 0

Re: [trinity-devel] tdelibs FTBFS: cmake 2.8.12: INTERFACE_LINK_LIBRARIES vs. LINK_INTERFACE_LIBRARIES
by Darrell Anderson 22 Dec '13

22 Dec '13

>Crap! It seems I finally found the exactly line that triggers the >cmake bug! =) Great! >Try this... > >PS: I'm not sure if it will break something in other nm-related >modules... >But it should repair the build of the tdelibs with the 2.8.12. >PPS: Also there could be some other similar issues in other >modules... You and Slavek seem to be on similar paths. He just attached a patch to bug report 1759. I'm in the middle of testing his patch now. I only just started but with Slavek's patch tdelibs finally finished the configuration without the infamous LINK_ONLY error and is compiling with 2.8.12. I still need to test with 2.8.12.1 and then backwards compatibility with 2.8.8. Darrell

2 1

Re: [trinity-devel] tdelibs FTBFS: cmake 2.8.12: INTERFACE_LINK_LIBRARIES vs. LINK_INTERFACE_LIBRARIES
by Darrell Anderson 22 Dec '13

22 Dec '13

>Try this patch... expected results are: ><cmake-2.8.12: works fine as always were >=cmake-2.8.12: no warnings; but the same LINK_ONLY-bla-bla error >/* I still >can't reproduce it, but I suspect it's because of some link flags >e.g. I >don't use hidden-visibility*/ >cmake-2.8.12.1: no warnings; clean build. Your patch works nicely with cmake <= 2.8.12.0 or 2.8.12.1. Builds are clean. As you noted, the patch does not help with 2.8.12.0. I receive the same exact LINK_ONLY failure. As noted, the problem is described in the gentoo bugzilla: https://bugs.gentoo.org/show_bug.cgi?id=490194 The bug report mentions a specific patch and the patch became part of cmake 2.8.12.1. To my understanding, there is no downstream fix for this breakage with 2.8.12.0. The best we will be able to do for Trinity packagers is to let them know that Trinity will not build with 2.8.12.0. I asked the Slackware maintainer to update Slackware 14.1 to cmake 2.8.12.1 and I referenced the gentoo bugzilla. All I can do now is wait and see. I believe the Slackware maintainer avoided problems with cmake 2.8.12.0 in that the 2.8.12.0 was not updated in the Slackware 14.1 release cycle until just before RC1, well after all of the KDE packages had been built. Very likely he never saw the same build failures because he used cmake 2.8.10.2 to build the KDE4 packages for Slackware 14.1. Darrell

2 1

Opinion of Trinity R14.0.0
by Darrell Anderson 22 Dec '13

22 Dec '13

All, In the upcoming R14.0.0 press release I would like to include one user and one developer opinion why they enjoy Trinity R14.0.0. These types of quotations are common in product related press releases. If you volunteer an opinion, please be aware that some kind of identity connection to you is necessary. That connection can be a well-known online alias, but birth names are preferred to enhance credibility. The reason is in case a reviewer or reporter decides to perform fact checking. The press release will not include email addresses or anything like that. Just a name that a reviewer or reporter can identify and through the contacts listed at the end of the press release, be able to contact you to validate or expand upon your opinion. Although many people prefer privacy, providing an opinion and a name in the press release could serve as a free publicity of your coding and project participation skills. Please limit opinions to a maximum of three sentences. If English is not your native language, please still feel welcome to offer an opinion. I'll help you massage the text. As primary developers, Tim and Slavek should be the main press release contact points, but that is a decision for both of you to make. A draft of the press release is available in the etherpads: http://trinity.etherpad.trinitydesktop.org/37 Please feel welcome to improve the draft. Please post any such opinions here to the dev mail list. I'll select two, although I might roll dice to perform the selection. :-) Thank you! Darrell

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels