From: Vaelatern <Vaelatern@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: xbps-src: simplify dbulk-dump output
Date: Sat, 13 Mar 2021 00:33:12 +0100 [thread overview]
Message-ID: <20210312233312.NhmhrdTKEvQMwfA8ooitCe2BK9drfjWgs8uJ61NsEqo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29387@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 977 bytes --]
There's a merged pull request on the void-packages repository
xbps-src: simplify dbulk-dump output
https://github.com/void-linux/void-packages/pull/29387
Description:
* List dependencies of subpackages as part of the source packages
dependencies, knowing the subpackage they are coming from does
not matter to a build scheduler as long as xbps-src requires
those to exist in the same way to main depends= have to exist.
* Resolve virtual? packages through existing means in xbps-src to
avoid duplicating and possibly diverting from xbps-src's
behaviour in tools that use dbulk-dump.
* Filter out dependencies on the template itself from sub packages,
this matches the xbps-src behaviour and there is no need to
have to duplicate logic for this into the scheduling tool.
* Error out on archs= restrictions as we do already on broken=
and nocross=, there shouldn't be the need to discover archs=
restrictions when attempting to build the package.
prev parent reply other threads:[~2021-03-12 23:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 21:07 [PR PATCH] " Duncaen
2021-03-10 21:10 ` [PR PATCH] [Updated] " Duncaen
2021-03-10 21:11 ` Duncaen
2021-03-10 21:23 ` ericonr
2021-03-12 23:33 ` Vaelatern [this message]
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=20210312233312.NhmhrdTKEvQMwfA8ooitCe2BK9drfjWgs8uJ61NsEqo@z \
--to=vaelatern@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).