Package Details: darkly 0.5.37-1

Git Clone URL: https://aur.archlinux.org/darkly.git (read-only, click to copy)
Package Base: darkly
Description: Fork of Lightly (A modern style for Qt applications)
Upstream URL: https://github.com/Bali10050/darkly
Keywords: plasma6-application-style
Licenses: GPL-2.0-or-later
Submitter: DeltaCopy
Maintainer: DeltaCopy
Last Packager: DeltaCopy
Votes: 8
Popularity: 1.20
First Submitted: 2024-12-21 22:02 (UTC)
Last Updated: 2026-03-24 02:02 (UTC)

Pinned Comments

Latest Comments

1 2 Next › Last »

Martchus commented on 2025-12-16 09:18 (UTC)

Why is the creation of the debug package disabled? That would make sense if it prevents the build for whatever reason. Otherwise I'd remove this option and let users decide whether they want that or not (by putting that option in their makepkg.conf).

vcalv commented on 2025-07-01 15:25 (UTC) (edited on 2025-07-01 16:12 (UTC) by vcalv)

Can you please use tar sources instead of git?

It's very wasteful to have to download the entire git repository even if you're only using one tag.

Also, why does this have a pkgver function? Tha upstream published actual releases, this is not a -git package.

Thank you.

In case anyone is interested:


# Maintainer: DeltaCopy <7x0bb03yq@mozmail.com>
# Description: Builds Darkly from https://github.com/Bali10050/Darkly
# Autogenerated from https://github.com/DeltaCopy/darkly-packager

# basic info
pkgname="darkly"
pkgver=0.5.21
pkgrel=1
pkgdesc="Fork of Lightly (A modern style for Qt applications)"
url="https://github.com/Bali10050/darkly"
arch=('x86_64' 'aarch64')
license=("GPL-2.0-or-later")
pkgdir="$srcdir/fakeinstall_kf6"
build_dir="build_kf6"

makedepends=(
  'cmake'
  'extra-cmake-modules'
)

options=(!emptydirs !debug)

source=(
    "${pkgname}-${pkgver}.tar.gz::https://github.com/Bali10050/Darkly/archive/refs/tags/v$pkgver.tar.gz"
)

sha256sums=(
  'bf3bd01d078850101182a7147e92300880ac6b21d5c1f35434d256e72d716524'
)

# KF6/Qt6
depends_kf6=(
  'kdecoration'
  'qt6-declarative'
  'kcoreaddons'
  'kcmutils'
  'kcolorscheme'
  'kconfig'
  'kguiaddons'
  'kiconthemes'
  'kwindowsystem'
  'frameworkintegration'
)

# KF5/QT5 for backward compatibility
depends_kf5=(
    'kcmutils5'
    'frameworkintegration5'
    'kconfigwidgets5'
    'kiconthemes5'
    'kirigami2'
    'kwindowsystem5'
)

depends=("${depends_kf6[@]}" "${depends_kf5[@]}")

build() {
  cd "$srcdir/Darkly-$pkgver"
  local cmake_options=(
    -B $build_dir
    -DBUILD_TESTING=OFF
    -Wno-dev
  )

  cmake "${cmake_options[@]}"
  cmake --build $build_dir
}

package() (
  cd "$srcdir/Darkly-$pkgver"
  DESTDIR="$pkgdir" cmake --install $build_dir
  rm -rf "$pkgdir/usr/lib/cmake"
)

Sving1024 commented on 2025-06-02 12:17 (UTC)

Should frameworkintegration be in the dependencies list too? Without the package, my qt6 applications cannot use Darkly properly.

DeltaCopy commented on 2025-02-03 10:53 (UTC)

@leo_sk

I cannot replicate this issue.

Using yay I am able to build and install this application style successfully. Which AUR helper are you using, and have you tried clearing out any cache files related to it.

leo_sk commented on 2025-02-02 20:01 (UTC)

Getting error


==> Validating source files with sha256sums...
    darkly.git ... fatal: not a valid object name: v0.5.15.r0.g1593f8b
==> ERROR: One or more files did not pass the validity check!

DeltaCopy commented on 2025-01-09 15:42 (UTC)

If you run into the following it is related to parallel compilation.

darklyconfigwidget.h:28:10: fatal error: config/ui_darklyconfigurationui.h: No such file or directory

You can configure parallel compilation inside: /etc/makepkg.conf

MAKEFLAGS="--jobs=$(nproc)"

For further details see: https://wiki.archlinux.org/title/Makepkg#Parallel_compilation

DeltaCopy commented on 2024-12-30 09:41 (UTC)

@OzzyHelix that shouldn't be the case with Darkly, also I don't see any related issues reported on the upstream URL.

1 2 Next › Last »