From: michalszmidt <michalszmidt@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] New package: supersonic-0.8.2
Date: Fri, 29 Dec 2023 20:01:45 +0100 [thread overview]
Message-ID: <20231229190145.wm1RLiyxT-yhuuKrhz4yHeb2uOgiiLVo2AE10Y-dFHc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47986@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1277 bytes --]
New review comment by michalszmidt on void-packages repository
https://github.com/void-linux/void-packages/pull/47986#discussion_r1438375460
Comment:
There's no clear statement about the proper package name
whether it is `supersonic` or `supersonic-desktop`.
Repo name is supersonic, our build system outputs `supersonic` executable, headbar title is Supersonic, flatpak manifest says `io.github.dweymouth.supersonic` so I decided to stick to it as pacakge name.
When it comes to other repos.
- AUR has both options, lol
- nixpgs prefers `supersonic`
- YACP prefers `supersonic`
Desktop file seems to be the only place where it's referred as `supersonic-desktop`
```diff
--- a 2023-12-29 19:42:39.628481930 +0100
+++ b 2023-12-29 19:42:46.588597726 +0100
@@ -4,7 +4,7 @@
Name=Supersonic
Comment=A lightweight cross-platform desktop client for Subsonic music servers
Path=/usr/bin
-Exec=supersonic-desktop
+Exec=supersonic
Terminal=false
-Icon=supersonic-desktop
+Icon=/usr/share/pixmaps/supersonic/appicon.png
Categories=Audio;AudioVideo
```
I suppose it could be tweaked to output `supersonic-desktop` but it'll complicate template file and it's easier to maintain desktop file that changes rarely rather than patch.
But you decide.
next prev parent reply other threads:[~2023-12-29 19:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-29 17:24 [PR PATCH] " michalszmidt
2023-12-29 17:44 ` [PR REVIEW] " classabbyamp
2023-12-29 19:01 ` michalszmidt [this message]
2023-12-29 19:03 ` classabbyamp
2023-12-29 19:04 ` classabbyamp
2023-12-29 19:43 ` [PR PATCH] [Updated] " michalszmidt
2023-12-29 19:43 ` michalszmidt
2023-12-29 19:47 ` [PR REVIEW] New package: supersonic-desktop-0.8.2 michalszmidt
2023-12-29 19:48 ` [PR PATCH] [Updated] " michalszmidt
2023-12-29 20:04 ` [PR REVIEW] " classabbyamp
2023-12-29 20:04 ` classabbyamp
2023-12-29 22:06 ` [PR PATCH] [Updated] " michalszmidt
2023-12-29 22:07 ` [PR REVIEW] " michalszmidt
2023-12-29 22:07 ` michalszmidt
2024-01-01 23:50 ` Johnnynator
2024-01-01 23:53 ` Johnnynator
2024-01-08 1:10 ` [PR PATCH] [Updated] " michalszmidt
2024-01-08 1:15 ` [PR REVIEW] " michalszmidt
2024-01-08 17:26 ` [PR PATCH] [Updated] " michalszmidt
2024-01-09 2:20 ` michalszmidt
2024-04-09 1:45 ` github-actions
2024-04-23 1:46 ` [PR PATCH] [Closed]: " github-actions
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=20231229190145.wm1RLiyxT-yhuuKrhz4yHeb2uOgiiLVo2AE10Y-dFHc@z \
--to=michalszmidt@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).