From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] vala-panel-appmenu missing dependencies
Date: Fri, 15 Dec 2023 07:27:05 +0100 [thread overview]
Message-ID: <20231215062705.BRxaPAH1cFT8rR3IxGCI6hpbZO0P71BqVuousCWtYOk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37064@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1354 bytes --]
Closed issue by sm-idk on void-packages repository
https://github.com/void-linux/void-packages/issues/37064
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt. However, a quality pull request may help. -->
### System
* xuname: Void 5.15.36_1 x86_64 AuthenticAMD uptodate rrrrrmmdnFFFFFFFF
*output of ``xuname`` (part of xtools)*
* package: vala-panel-appmenu-0.7.6_2
*affected package(s) including the version*: ``xbps-query -p pkgver <pkgname>``
### Expected behavior
Package should pull `libdbusmenu-gtk3`, `libdbusmenu-qt5` alongside just `libdbusmenu-glib` so all windows that want to use the appmenu functionality will work with `vala-panel-appmenu` out of the box. (possible that it needs `appmenu-gtk-module`, `appmenu-gtk3-module` and `appmenu-registrar` along with it, but i didn't test that out yet)
### Actual behavior
None of the packages are dependencies of the `vala-panel-appmenu` package, making `vala-panel` and `vala-panel-appmenu` have the same functionality
### Steps to reproduce the behavior
```sh
# xbps-install vala-panel-appmenu
$ vala-panel -p appmenu #This will not work
```
```sh
# xbps-install vala-panel-appmenu libdbusmenu-gtk3 libdbusmenu-qt5
$ vala-panel -p appmenu #This will work as intended
```
prev parent reply other threads:[~2023-12-15 6:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 17:39 [ISSUE] " sm-idk
2022-08-26 20:24 ` glaulher
2022-08-26 20:26 ` glaulher
2023-12-15 6:27 ` sgn
2023-12-15 6:27 ` sgn [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231215062705.BRxaPAH1cFT8rR3IxGCI6hpbZO0P71BqVuousCWtYOk@z \
--to=sgn@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).