From: Chocimier <Chocimier@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: xbps-src: overwrite packages in local repo
Date: Mon, 23 Aug 2021 20:26:48 +0200 [thread overview]
Message-ID: <20210823182648.DHUOt-2yE8z-L1EExSKkvE4rOk0VHE1jWunRZHA9id0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32560@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 723 bytes --]
New comment by Chocimier on void-packages repository
https://github.com/void-linux/void-packages/pull/32560#issuecomment-904009030
Comment:
Added `-f`, simplified `XBPS_TARGET_MACHINE`.
As for unsetting XBPS_PRESERVE_PKGS with flag, is this really more useful than unsetting XBPS_CHECK_PKGS? Do we want parity between flags and variables in general?
For documentation, anything more needed?
> if there suddenly appears a new subpackage
Well, as proposed, xbps-src only looks whether package from command line argument is there, and if not, it overrides all other packages build together. IMO good enough and better than as is, i.e. preserve existing packages but index new, possibly with conflicting files.
next prev parent reply other threads:[~2021-08-23 18:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 23:11 [PR PATCH] " Chocimier
2021-08-18 2:49 ` [PR REVIEW] " ericonr
2021-08-23 18:03 ` [PR PATCH] [Updated] " Chocimier
2021-08-23 18:19 ` Chocimier
2021-08-23 18:26 ` Chocimier [this message]
2021-08-30 17:18 ` Chocimier
2021-08-30 17:33 ` Chocimier
2021-09-06 20:37 ` Chocimier
2021-09-08 20:36 ` Chocimier
2021-09-13 21:03 ` [PR PATCH] [Updated] " Chocimier
2021-09-13 21:04 ` [PR PATCH] [Merged]: " Chocimier
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=20210823182648.DHUOt-2yE8z-L1EExSKkvE4rOk0VHE1jWunRZHA9id0@z \
--to=chocimier@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).