void-linux / void-linux/void-packages

Package request: Bluejay

Open
#55,570 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

request
Dominant language
Shell
Stars
3.4k
Forks
2.8k
Avg merge
2d 5h
Merged PRs (30d)
299

Description

Package name

Bluejay

Package homepage

https://github.com/EbonJaeger/bluejay

Description

Qt ile yazılmış Bluetooth yöneticisi

A nice alternative for Blueman

Image

# Template file for 'Bluejay'
pkgname=Bluejay
version=1.0.2
revision=1
build_style=cmake
hostmakedepends="qt6-tools-devel extra-cmake-modules gettext-devel"
makedepends="qt6-base-devel qt6-declarative-devel kf6-bluez-qt-devel 
 kf6-kcoreaddons-devel kf6-kdbusaddons-devel kf6-ki18n-devel 
 kf6-kirigami-devel kf6-qqc2-desktop-style-devel kirigami-addons-devel"
depends="qt6-base qt6-declarative"
short_desc="Bluetooth manager written in Qt"
maintainer="void <hello@hello.world>"
license="MPL-2.0"
homepage="https://github.com/EbonJaeger/bluejay"
distfiles="https://github.com/EbonJaeger/bluejay/archive/refs/tags/v${version}.tar.gz"
checksum=3306c1dcbb1bd8bc6b5c0e1cc9a8f9c53eedeb019cbf09196362526081cf8bf8

post_install() {
    vlicense LICENSE
}
Does the requested package meet the package requirements?

System

Is the requested package released?

No

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the upstream Bluejay homepage and the supplied template, first confirming whether version 1.0.2 is a released source archive and whether the listed Qt/KF6 dependencies fit Void's package requirements. Done means a validated package request or template that meets those requirements; the issue currently says the software is not released.

Written by the indexing model from the issue text.

Assessment

Tech stack
cmake, shell
Domain
build-system, desktop
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.