Github messages for voidlinux
 help / color / mirror / Atom feed
From: anjandev <anjandev@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: zzz-user-hooks-1.0.0
Date: Sat, 11 Jul 2020 23:58:47 +0200	[thread overview]
Message-ID: <20200711215847.qE400624CgycHD_rmY88v2Qwt5xOxYWkGBG5hdVBnnY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23430@inbox.vuxu.org>

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

New comment by anjandev on void-packages repository

https://github.com/void-linux/void-packages/pull/23430#issuecomment-657136521

Comment:
Hey,

Andrew J. Hesford <notifications@github.com> writes:

> This can be bumpbed to 1.1.0 and the `sudo` dependency removed, right?

Sorry I have been busy. I updated to 1.1.0 and removed sudo as a
dependency. Please merge this if you think it's ready.

> The X11 and Wayland detection in the upstream project is a little hacky, but that mean it isn't useful or suitable for packaging.

What would be the ideal way to detect X11 or Wayland? I can notify the
maintainer of the better way.

Thanks,
Anjandev Momi


  parent reply	other threads:[~2020-07-11 21:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23430@inbox.vuxu.org>
2020-07-06 23:48 ` [PR REVIEW] " sgn
2020-07-06 23:48 ` sgn
2020-07-06 23:58 ` [PR PATCH] [Updated] " anjandev
2020-07-07  0:00 ` [PR REVIEW] " anjandev
2020-07-07  0:00 ` anjandev
2020-07-07  0:01 ` [PR PATCH] [Updated] " anjandev
2020-07-11 20:23 ` [PR REVIEW] " ahesford
2020-07-11 21:54 ` [PR PATCH] [Updated] " anjandev
2020-07-11 21:58 ` anjandev [this message]
2020-07-12  3:29 ` ahesford
2020-07-23 14:10 ` sgn
2020-07-23 14:33 ` ahesford
2020-07-23 14:34 ` [PR PATCH] [Merged]: " sgn

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=20200711215847.qE400624CgycHD_rmY88v2Qwt5xOxYWkGBG5hdVBnnY@z \
    --to=anjandev@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).