Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

pkgkde-override-sc-dev-latest(1) [debian man page]

PKGKDE-OVERRIDE-SC-DEV-LATEST(1)			User Contributed Perl Documentation			  PKGKDE-OVERRIDE-SC-DEV-LATEST(1)

NAME

       pkgkde-override-sc-dev-latest - loosen kde-sc-dev-latest Break restrictions

SYNOPSIS

       pkgkde-override-sc-dev [-bbase_version] [-vversion]

DESCRIPTION

       pkgkde-override-sc-dev-lastest is a helper utility which can be used to generate a dummy kde-sc-dev-latest package without Breaks field
       that is present in the original version. Original kde-sc-dev-latest package is used to force KDE Software Compilation modules to be built
       against the latest version of the KDE Development Platform modules without bumping versions of a bunch build dependencies for each KDE SC
       module. However, while original kde-sc-dev-latest does not cause problems when building in clean chroots, the restrictions imposed by its
       Breaks field might be undesirable on the maintainer system when:

       o   the maintainer wants to (test)build KDE module version X.Y.A against KDE Development Platform X.Y.B where (A > B);

       o   the maintainer builds a new upstream version of the some KDE Development Platform module on the system that has an old version of some
	   KDE Development Platform packages installed. For example, even if kdepimlibs does not build depend on kdebase-workspace-dev, original
	   kde-sc-dev-latest may prevent kdepimlibs X.Y.A to be built on the system which has kdebase-workspace X.Y.B (where A > B) installed.

       By default, pkgkde-override-sc-dev-latest generates a dummy kde-sc-dev-latest package in the current working directory that is based on the
       current "candidate" version of the original kde-sc-dev-latest (as per apt-cache policy). You may specify a base version with the -b option.
       The resulting dummy kde-sc-dev-latest override package will have "base_version+override" as its version unless another one is specified
       with -v option. Once the package is generated, you can install it like:

	 # dpkg --install kde-sc-dev_<version>+override_all.deb

OPTIONS

       -bbase_version, --basever=base_version
	   The version of the original kde-sc-dev-latest package to base an override package on. It must be available in the APT database on the
	   system. You may also pass special value "latest" to select the latest available version in the APT database. If you specify "priority",
	   the latest version with the highest priority will be selection. By default (if this option is not specified), candidate version is
	   selected

       -vversion, --version=version
	   Generate an override package with the specified "version+override" rather than default "base_version+override" version.

AUTHOR

       Modestas Vainius <modax@debian.org>

perl v5.14.2							    2011-12-26					  PKGKDE-OVERRIDE-SC-DEV-LATEST(1)

Check Out this Related Man Page

KDEINIT4(8)							 KDE User's Manual						       KDEINIT4(8)

NAME

       kdeinit4 - KDE process launcher.

SYNOPSIS

       kdeinit4 [--help] [[--no-fork] | [--no-kded] | [--suicide]] [[+programs] | [programs]]

DESCRIPTION

       kdeinit4 is a process launcher somewhat similar to the famous init used for booting UNIX. It executes KDE programs and kdeinit loadable
       modules (KLMs) starting them more efficiently.

       Using kdeinit4 to launch KDE applications makes starting a typical KDE application a couple times faster and reduces memory consumption by
       a substantial amount.

       kdeinit4 is linked against all libraries a standard KDE application needs. With this technique, starting an application becomes much faster
       because now only the application itself needs to be linked whereas otherwise both the application as well as all the libaries it uses need
       to be linked.

DISADVANTAGES

       The process name of applications started via kdeinit4 is "kdeinit4". This problem can be corrected to a degree by changing the application
       name as shown by ps. However, applications like killall will only see kdeinit4 as the process name. To workaround this, use kdekillall
       (from kdesdk/scripts) for applications started via kdeinit4.

OPTIONS

       --help
	   Show help about options

       --no-fork
	   Do not fork, i.e. do not exit until all the executed programs ends

       --no-kded
	   Do not start kded

       --suicide
	   Terminate when no KDE applications are left running

       +programs
	   runs the programs handling requests

       programs
	   runs the programs without handling requests

USAGE

       A standard way to run this program is by simply specifying the following command at the prompt kdeinit4 program or kdeinit4 +program

FILES

       /tmp/kde-$USER/kdeinit4_$INSTANCE
	   ...

ENVIRONMENT VARIABLES

       $HOME
	   Specifies the home directory of the current user

       $KDE_HOME_READONLY
	   Specifies if the home directory of the current user is read only

       $KDE_IS_PRELINKED
	   If set, tells kdeinit4 that the KDE programs are pre-linked.

	   (Prelinking is a process that allows you to speed up the process of dynamic linking.)

       $KDE_DISPLAY
	   If set, tells kdeinit4 that it is running on a KDE desktop.

SEE ALSO

       kded, kdekillall

BUGS

       There are probably tons of bugs. Use bugs.kde.org[1] to report them.

AUTHORS

       Waldo Bastian <bastian@kde.org>
	   Author.

       Mario Weilguni <mweilguni@sime.com>
	   Author.

       Lubos Lunak <l.lunak@kde.org>
	   Author.

NOTES

	1. bugs.kde.org
	   http://bugs.kde.org

0.01.01 							    2008-10-03							       KDEINIT4(8)
Man Page