From: st3r4g <st3r4g@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC] libglvnd: depend on mesa
Date: Sun, 01 Nov 2020 07:53:37 +0100 [thread overview]
Message-ID: <20201101065337.NsDyAx5Vo_sTIcpMETXMvD3kT0wCcBQe7CxERerDIoM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18712@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 659 bytes --]
New comment by st3r4g on void-packages repository
https://github.com/void-linux/void-packages/pull/18712#issuecomment-720044085
Comment:
Ah yes, this would reintroduce the build cycle. So maybe let's freeze the other PR until we arrive at a decision here.
Anyway, I don't like this PR. The alternative to solve this problem would be to make xbps-src "less strict" with rundeps. I have thought to make it build all rundeps after the dependant instead of before, but that is probably a too drastic change from current behaviour. Or maybe introduce some way to tell it to skip building when it's safe to do so, but it could be misused... what do you think?
next prev parent reply other threads:[~2020-11-01 6:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-01 13:59 [PR PATCH] " voidlinux-github
2020-02-01 14:01 ` voidlinux-github
2020-02-01 14:02 ` voidlinux-github
2020-02-01 16:58 ` voidlinux-github
2020-02-01 17:15 ` voidlinux-github
2020-02-03 7:13 ` voidlinux-github
2020-02-03 10:57 ` voidlinux-github
2020-11-01 2:30 ` ericonr
2020-11-01 6:53 ` st3r4g [this message]
2020-11-02 0:12 ` ericonr
2021-01-04 13:55 ` st3r4g
2021-01-04 14:10 ` ericonr
2022-04-15 2:13 ` github-actions
2022-04-29 2:13 ` [PR PATCH] [Closed]: " github-actions
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=20201101065337.NsDyAx5Vo_sTIcpMETXMvD3kT0wCcBQe7CxERerDIoM@z \
--to=st3r4g@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).