pkg-kde-tools 0.15.36-ok1 source package in openKylin

Changelog

pkg-kde-tools (0.15.36-ok1) yangtze; urgency=medium

  * Build for openkylin.

 -- sufang <email address hidden>  Wed, 07 Sep 2022 14:13:12 +0800

Upload details

Uploaded by:
sufang
Sponsored by:
Cibot
Uploaded to:
Yangtze V1.0
Original maintainer:
Openkylin Developers
Architectures:
any
Section:
devel
Urgency:
Medium Urgency

Publishing See full publishing history

Series Pocket Published Component Section
Yangtze V1.0 release main devel
Yangtze V1.0 proposed main devel

Downloads

File Size SHA-256 Checksum
pkg-kde-tools_0.15.36.orig.tar.gz 1.1 MiB 48ba89b738b1634ed2f6e023573941d7f1175c1338f36695f88c354c518688db
pkg-kde-tools_0.15.36-ok1.debian.tar.xz 24.6 KiB 2e9c396a0a37a1b805213ba344cb97e285944993bb5d7fb1abfa21bf194f0909
pkg-kde-tools_0.15.36-ok1.dsc 1.9 KiB 6e4664df17d59f857bbea7025f5f6b7c76155329d52d38b6664937527535506f

View changes file

Binary packages built by this source

libdlrestrictions-dev: development files for the DLRestrictions library

 This package provides development files needed to build both shared libraries,
 which specify their compatibility restrictions, and applications, which check
 whether those restrictions are satisfied before using those libraries. The
 package also contains a CMake module which simplifies building DLRestricted
 shared libraries with CMake.

libdlrestrictions1: library that implements library compatibility checks for dlopen()

 This package provides a DLRestrictions library that can be used to check
 compatibility of the external shared library (or plugin) against other
 libraries currently loaded in the global symbol object. It might help to avoid
 symbol clashes and provide means for graceful failure detection in advance
 before the first dlsym() call. Otherwise, usage of incompatible library might
 result in crashes or other unpredictable failures of the application.
 .
 A shared library that is protected by DLRestrictions provides a special symbol
 which defines conditions under which the library may be safely used. At the
 moment, the only restriction that may be imposed controls whether multiple
 SONAMEs of the same library can safely co-exist in the same symbol space.
 Shared library dependencies are also checked for compatibility.

libdlrestrictions1-dbgsym: debug symbols for libdlrestrictions1
pkg-kde-tools: various packaging tools and scripts for KDE Applications

 This package contains a variety of packaging tools and build scripts that may
 be very useful when packaging KDE applications. Even if you are a maintainer
 of a very small KDE application, this package should be worthwhile checking
 out.
 .
 Main highlights:
  - recommended build flags for building packages based on the KDE Platform;
  - cdbs class for building packages based on the KDE Platform (kde.mk);
  - debhelper build system (--buildsystem=kde) and dh addon (--with kde) for
    building packages based on the KDE Platform;
  - dh_sameversiondep for generating a dependency that is versioned the same
    way as a dependency (coming from the same source) of another reference
    package.
  - dh_movelibkdeinit for moving libkdeinit4_*.so libraries to private
    location;
  - dh_sodeps (and sodeps dh addon) for generating so:Depends substvar for -dev
    packages based to which local packages lib*.so symlinks point to;
  - dh_qmlcdeps (and qmlcdeps dh addon) for generating qmlc:Depends substvar
    for packages shipping QML cache files.
  - pkgkde-symbolshelper tool for efficient management of C and C++ symbol
    files;
  - pkgkde-debs2symbols tool for generating symbol files and symbol file
    patches from pre-built binaries in the deb packages;
  - pkgkde-getbuildlogs tool for downloading build logs for the specified
    package (from buildd.debian.org);
  - pkgkde-override-sc-dev-latest tool for overriding Breaks of the
    kde-sc-dev-latest package;
  - pkgkde-vcs tool for performing common tasks when packaging under VCS.
 .
 NOTE: since this package is cumulative, it does not depend on the packages it
 provides helpers for. I.e. you still need to explicitly build depend on
 debhelper or cdbs in your packages.