From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Automatically detect `XBPS_SUCMD` if not set
Date: Wed, 17 May 2023 00:07:55 +0200 [thread overview]
Message-ID: <20230516220755.wj-xZ6Ie5RteTIyZpNjMINHH-ENF5mM2t_zpLKxJTd8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38075@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 440 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/issues/38075#issuecomment-1550417905
Comment:
please don't put this anywhere where it will be executed each xbps-src invocation. There are tools that execute xbps-src in a loop on many packages to gather dependencies and each fork is expensive, this function would add a bunch of forks for something that is only required for one sub command.
next prev parent reply other threads:[~2023-05-16 22:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 21:32 [ISSUE] " paper42
2022-10-13 2:15 ` github-actions
2023-01-12 2:28 ` github-actions
2023-05-16 15:19 ` Clos3y
2023-05-16 16:24 ` classabbyamp
2023-05-16 20:55 ` Clos3y
2023-05-16 22:07 ` Duncaen [this message]
2023-05-16 22:09 ` Duncaen
2023-05-17 8:07 ` Clos3y
2023-05-17 21:18 ` Clos3y
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=20230516220755.wj-xZ6Ie5RteTIyZpNjMINHH-ENF5mM2t_zpLKxJTd8@z \
--to=duncaen@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).