Github messages for voidlinux
 help / color / mirror / Atom feed
From: CtrlC-Root <CtrlC-Root@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package request: Update existing libspnav to 1.1
Date: Wed, 21 Jun 2023 18:47:13 +0200	[thread overview]
Message-ID: <20230621164713.wyYsHqDNBCBma57UsbBdSFnyH-9_sZqO9lD77cfHf-U@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44550@inbox.vuxu.org>

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

New comment by CtrlC-Root on void-packages repository

https://github.com/void-linux/void-packages/issues/44550#issuecomment-1601204609

Comment:
I see that but it's not clear to me what to do when the change is more than updating to a new version. Did I miss some part of the documentation that talks about the process for this? Specifically:

>     * The releases are now available on GitHub (see links above).

And Sourceforge no longer has the newer release. So it's not just a package version update.

![image](https://github.com/void-linux/void-packages/assets/4819590/eff2963b-a9c4-4151-ba3f-e6ae1c7205bf)

>     * The new version supports a non-X11 build as well as the X11 build. It would be nice to have both as variants although I'm not familiar enough with XBPS to know if this is possible or how it would work.

Should these be separate packages? How does this work in XBPS?

  parent reply	other threads:[~2023-06-21 16:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-21 14:20 [ISSUE] " CtrlC-Root
2023-06-21 16:29 ` classabbyamp
2023-06-21 16:29 ` [ISSUE] [CLOSED] " classabbyamp
2023-06-21 16:47 ` CtrlC-Root [this message]
2023-06-21 16:58 ` CtrlC-Root
2023-07-13 18:34 ` CtrlC-Root

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=20230621164713.wyYsHqDNBCBma57UsbBdSFnyH-9_sZqO9lD77cfHf-U@z \
    --to=ctrlc-root@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).