Translations talk:Installing third party softwares in terminal/Increased Productivity in KDE4 with Scripts/.bashrc

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

I'm not sure whether this is right. This page is only used from Getting Started/Build/KDE4 but it is a subpage of Increased ... with Scripts.

--Dhaumann 16:38, 24 February 2007 (CET)


What is it for? I don't need. I't works fine without it.

KDevelop Generator

Would it not be a good idea to have cmakekde use the KDevelop generator by default?

--Gavinbeatty 18:07, 15 June 2007 (CEST)

Scripts and bashrc in SVN

Wouldn't it be better to put this and similar stuff in SVN? A location such as (a cleaned up) KDE/trunk/kdesdk/scripts ?

--Gavinbeatty 18:07, 15 June 2007 (CEST)


Seeing as this script adds many static environment variables and "increments" others, would it not be better to have it as a separate bash_profile (for the static/non-interactive stuff) and bashrc (interactive stuff e.g., functions) instead? The functions etc should still be sourced by the user's bashrc

--Gavinbeatty 18:07, 15 June 2007 (CEST)

A new cmakekdeall?

I would like to replace the cmakekdeall shell function with the following version:

function cmakekdeall {

        FOLDERS="kdesupport KDE/kdelibs KDE/kdebase \
                KDE/kdepimlibs KDE/kdepim KDE/kdesdk \
                KDE/kdegraphics KDE/kdevplatform KDE/kdevelop \
                # Add others or remove to taste, e.g.
                # KDE/kdemultimedia KDE/kdenetwork KDE/kdeutils \

        cd && cs # go to src root
        svn up $FOLDERS

        for f in $FOLDERS; do
            cs $f && cmakekde || return


This improves the existing function in two respects:

  1. It fetches the sources in a single svn command. Although I'm not sure it guarantees a single version, it certainly improves the chances for it, and helps consistency. The current version builds each module after fetching it, so not only are there separate svn commands, there are significant time gaps between their invocations. (Note: In the scheme set up in the tutorials, the different folders are each checked out separately -- src/KDE is not a SVN working copy).
  2. In case of build failure, the process stops.

Michael Pyne on kde-devel suggested that stopping on every failure may not be desirable, but I think at least for newbies (as I consider myself to be one) this is better.

Any other comments?

Thanks, Shai 23:07, 5 January 2009 (UTC).


I noticed that the XDG vars have been changed. The command used to be:

unset XDG_DATA_DIRS # to avoid seeing kde3 files from /usr

but now is:

#unset XDG_DATA_DIRS # to avoid seeing kde3 files from /usr
prepend XDG_DATA_DIRS $KDEDIR/share

Installing with the new commands made my icons disappear and the "Could not find mime type" errors appearing in several applications.

--Aoszkar 14:31, 19 May 2010 (UTC)

This page was last edited on 2 February 2011, at 02:09. Content is available under Creative Commons License SA 4.0 unless otherwise noted.