Github messages for voidlinux
 help / color / mirror / Atom feed
From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC] optionally set GOPROXY, GOSUMDB when building go packages
Date: Sat, 29 Apr 2023 13:03:07 +0200	[thread overview]
Message-ID: <20230429110307.HS-5HwDjvq44kOYIrTdhZLwtQWYLwTdmYBWRiGa-FJc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43668@inbox.vuxu.org>

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

New comment by ahesford on void-packages repository

https://github.com/void-linux/void-packages/pull/43668#issuecomment-1528759384

Comment:
Adding magic to XBPS really only makes sense if it impacts more than a couple of templates. If you have a template that would benefit from this (and, if so, why isn't it being modified to use these features here?), you might as well just export the variables directly and add the dependencies you require. 

  parent reply	other threads:[~2023-04-29 11:03 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-29  9:16 [PR PATCH] " hazen2215
2023-04-29  9:18 ` classabbyamp
2023-04-29  9:21 ` classabbyamp
2023-04-29  9:33 ` [PR PATCH] [Updated] " hazen2215
2023-04-29  9:49 ` hazen2215
2023-04-29  9:49 ` hazen2215
2023-04-29  9:49 ` hazen2215
2023-04-29  9:50 ` hazen2215
2023-04-29  9:50 ` hazen2215
2023-04-29  9:52 ` hazen2215
2023-04-29 10:15 ` classabbyamp
2023-04-29 11:03 ` ahesford [this message]
2023-04-29 11:07 ` hazen2215
2023-04-29 11:20 ` hazen2215
2023-07-29  1:48 ` github-actions
2023-07-29  3:22 ` [PR PATCH] [Updated] " hazen2215
2023-08-23 22:17 ` hazen2215
2023-11-22  1:47 ` github-actions
2023-11-22  2:47 ` [PR PATCH] [Updated] " hazen2215
2024-01-05  1:57 ` hazen2215
2024-04-05  1:45 ` github-actions
2024-04-05  2:34 ` [PR PATCH] [Updated] " hazen2215

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=20230429110307.HS-5HwDjvq44kOYIrTdhZLwtQWYLwTdmYBWRiGa-FJc@z \
    --to=ahesford@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).