In addition to filelight-l10n (which I don't use too, even though I haven been building it), applications/kuickshow and mlt/mlt++, I am also thinking about knetworkmanager8 and kpowersave. AFAIK, they have been replaced by tdenetworkmanager and tdepowersave and I don't use them anymore (knetworkmanager8 also FTBFS). Slavek, in the git packaging repo, under Ubuntu there are a lot of folders. Are they all necessary or can we purge some? I am thinking about lucid_automake and maverick_automake, plus the 'kdegraphics.automake' and 'kdevelop.cmake' that are in almost all Ubuntu distros. There may be some more, but in general I wonder if we can do a little of clean-up. Debian distros packaging folders are much cleaner IMO.

IMO, I would prefer a GIT repo which is relevant to the current development trunk (less code to maintain, less code to look through in case of bug searching, less code to build, less building time, less of all :) ) Yes, some of the mentioned packages may be required for building older TDE versions (such as 3.5.13), but we have tags and as I already said, a simple git checkout would restore your local repo to the exact point of when a particular version was tagged and built in a matter of seconds, including folders no longer present in the current repo. Anyhow, just my 2 cents. Cheers Michele

I have opened the bug: http://bugs.pearsoncomputing.net/show_bug.cgi?id=1937

There are still those building from the tree that use the qt3/3.5.13 codebase. All of the directories applicable to that build knetworkmanager8, etc. should remain in the tree.

With knetworkmanager8 is another problem. As I recently discovered with dismay, backend for NetworkManager in tdehw-lib only supports NetworkManager 9 and later. With NetworkManager 8 does not work. Therefore, it is necessary either add support for NetworkManager 8 to tdehw-lib or fix knetworkmanager8. http://trinity-devel.pearsoncomputing.net/?0::12085 http://trinity-devel.pearsoncomputing.net/?0::12089

Le 16/02/2014 12:58, Michele Calgaro a écrit : Hello, Networkmanager 0.8 is used in RHEL 6, which will be supported until the end of year 2023. (it was released in 2011) https://access.redhat.com/site/support/policy/updates/errata/ So there are some professional users (like me) which would be interested in NM 0.8 support ... About tdepowersave, I believe that the current powersaving features in R14 already work in RHEL6. Francois

I doggy On Feb 16, 2014 9:06 AM, "Slávek Banko" <slavek.banko(a)axis.cz> wrote: > On Sunday 16 of February 2014 12:58:55 Michele Calgaro wrote: > > >With knetworkmanager8 is another problem. As I recently discovered with > > >dismay, backend for NetworkManager in tdehw-lib only supports > > > NetworkManager 9 and later. With NetworkManager 8 does not work. > > > Therefore, it is necessary either add support for NetworkManager 8 to > > > tdehw-lib or fix knetworkmanager8. > > > http://trinity-devel.pearsoncomputing.net/?0::12085 > > >http://trinity-devel.pearsoncomputing.net/?0::12089 > > > > Ah ah! I didn't know that, thanks. So knetworkmanager8 is still > relevant to > > the trunk and will have to stay until support for NM0.8 is added to > > tdehw-lib. What about kpowersave? Is it still needed for some reasons? > > > > Cheers > > Michele > > > > Theoretically, there could be a need to use kpowersave. Because tdehw-lib > is > based on the sysfs, it is bound to the Linux kernel. If anyone will be > interested in TDE on another Unix system, then will either have to use > HAL or > implement tdehw-lib for another kernel. > > -- > Slavek > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > trinity-devel-unsubscribe(a)lists.pearsoncomputing.net > For additional commands, e-mail: > trinity-devel-help(a)lists.pearsoncomputing.net > Read list messages on the web archive: > http://trinity-devel.pearsoncomputing.net/ > Please remember not to top-post: > http://trinity.pearsoncomputing.net/mailing_lists/#top-posting > >