Github messages for voidlinux
 help / color / mirror / Atom feed
From: loosefish-scapegrace <loosefish-scapegrace@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: xnotify-0.9.3
Date: Mon, 06 Nov 2023 05:31:44 +0100	[thread overview]
Message-ID: <20231106043144.LZ4-hP1fTdw7z406YUyT2L03zZK-OxfUdRTPmVNtaak@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47018@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1248 bytes --]

New comment by loosefish-scapegrace on void-packages repository

https://github.com/void-linux/void-packages/pull/47018#issuecomment-1794069322

Comment:
"Andrew J. Hesford" ***@***.***> wrote:
> @ahesford commented on this pull request.
> 
> 
> 
> > @@ -0,0 +1,24 @@
> +# Template file for 'xnotify'
> +pkgname=xnotify
> +version=0.9.3
> +revision=1
> +build_style=gnu-makefile
> +makedepends="imlib2-devel libXft-devel libX11-devel libXinerama-devel"
> +short_desc="Read notifications from stdin and pop them up on the screen"
> +maintainer="népéta ***@***.***>"
> +license="MIT"
> +homepage="https://github.com/phillbush/xnotify"
> +distfiles="https://github.com/phillbush/xnotify/archive/refs/tags/v0.9.3.tar.gz"
> +checksum=9fa7505ad16c8d5e2305a56d0d88ca3a7e324816b4df7845b920db088482eb24
> +
> +do_build() {
> +	[ -e ${FILESDIR}/config.h ] && cp ${FILESDIR}/config.h config.h
> 
> That's even more of an argument against adding this capability. Some future release will drop it entirely and we'll be left with vestigial logic that only existed to support custom builds in the first place.

That's fair, I think. `xnotify` supports Xresources anyway, so I
think it's not as useful as for something like `dmenu`...


  parent reply	other threads:[~2023-11-06  4:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-02  9:23 [PR PATCH] " loosefish-scapegrace
2023-11-04 20:00 ` [PR REVIEW] " Luciogi
2023-11-04 21:18 ` classabbyamp
2023-11-04 23:18 ` sh1r4s3
2023-11-04 23:24 ` sh1r4s3
2023-11-04 23:36 ` ahesford
2023-11-04 23:36 ` ahesford
2023-11-04 23:44 ` loosefish-scapegrace
2023-11-05 17:18 ` ahesford
2023-11-06  4:31 ` loosefish-scapegrace [this message]
2023-11-06  4:32 ` loosefish-scapegrace
2023-11-06  4:32 ` [PR REVIEW] " loosefish-scapegrace
2023-11-06  4:57 ` [PR PATCH] [Updated] " loosefish-scapegrace
2023-11-06  4:59 ` loosefish-scapegrace
2024-02-05  1:45 ` github-actions
2024-02-20  1:44 ` [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=20231106043144.LZ4-hP1fTdw7z406YUyT2L03zZK-OxfUdRTPmVNtaak@z \
    --to=loosefish-scapegrace@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).