Github messages for voidlinux
 help / color / mirror / Atom feed
From: abenson <abenson@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: Bump to v0.10.9 release, fix URLs, add dependencies
Date: Sat, 06 Nov 2021 22:47:13 +0100	[thread overview]
Message-ID: <20211106214713.OYPebi1ju5fuciGPze0WA-XZub4F0018kDecfRuY6MU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18306@inbox.vuxu.org>

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

There's a closed pull request on the void-packages repository

Bump to v0.10.9 release, fix URLs, add dependencies
https://github.com/void-linux/void-packages/pull/18306

Description:
- [x] Bump release
- [x] Update project URLs (moved to GitHub org since last release)
- [x] Update checksum
- [x] Add `--with-system-luarocks`. Note this is a new option since the last release, _not_ the default, but probably an option in keeping with Void Linux _MO_.
- [ ] Needs new packages for new dependencies not currently available:
    - [ ] lua-epnf
    - [x] lua-cassowary
    - [ ] lua-cosmo
    - [ ] lua-linenoise
    - [ ] lua-repl
    - [ ] lua-penlight
    - [ ] lua-vstruct
    - [ ] lua-stdlib
- [ ] Add documentation PDF as users manual
- [ ] Make sure (new) man page gets packaged

Some of these Lua packages that are missing were required by the previous version too (e.g. stdlib) so I'm not sure what's going on here.

If there is anything we can do upstream in SILE to make packaging easier let me know, I'm happy to facilitate a point release if 

  parent reply	other threads:[~2021-11-06 21:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-14 11:28 [PR PATCH] Bump to v0.10.0 " voidlinux-github
2020-01-14 15:05 ` voidlinux-github
2020-01-14 15:28 ` voidlinux-github
2020-01-14 16:29 ` voidlinux-github
2020-01-14 16:37 ` voidlinux-github
2020-02-05 10:00 ` voidlinux-github
2020-07-24 11:21 ` [PR PATCH] [Updated] Bump to v0.10.3 " alerque
2020-07-24 11:22 ` alerque
2020-07-24 13:14 ` [PR PATCH] [Updated] " alerque
2020-07-24 13:42 ` alerque
2020-07-24 13:52 ` [PR PATCH] [Updated] Bump to v0.10.9 " alerque
2020-12-20  2:10 ` [PR REVIEW] " ericonr
2020-12-20  7:32 ` alerque
2021-01-29  3:49 ` ericonr
2021-11-06 21:47 ` abenson [this message]
2021-11-06 21:47 ` abenson

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=20211106214713.OYPebi1ju5fuciGPze0WA-XZub4F0018kDecfRuY6MU@z \
    --to=abenson@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).