Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: Bump to v0.10.0 release, fix URLs, add dependencies
Date: Tue, 14 Jan 2020 17:37:37 +0100	[thread overview]
Message-ID: <20200114163737.xlGx5dYUnno1NPdjlt7nC2ik2pUXoXGWOG2dqS4NKtY@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: 645 bytes --]

New comment by alerque on void-packages repository

https://github.com/void-linux/void-packages/pull/18306#issuecomment-574262581

Comment:
@q66 There is already a vendor option built in. If Void people want this package to go that way all that has to happen is drop the assorted Lua package dependencies, make sure `luarocks` _is_ a dependency, and pass `/.configure` the `--without-system-luarocks` flag (or no flag at all since that's the default, I was expecting the opposite to get added somehow here.

I don't actually use Void Linux and don't care which way this goes, I'm just trying to facilitate downstream packages getting updated.

  parent reply	other threads:[~2020-01-14 16:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-14 11:28 [PR PATCH] " 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 [this message]
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
2021-11-06 21:47 ` [PR PATCH] [Closed]: " 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=20200114163737.xlGx5dYUnno1NPdjlt7nC2ik2pUXoXGWOG2dqS4NKtY@z \
    --to=voidlinux-github@inbox.vuxu.org \
    --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).