From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: etc/conf: implement XBPS_MIRROR for remote repos
Date: Mon, 06 Dec 2021 03:52:15 +0100 [thread overview]
Message-ID: <20211206025215.VKjObRhEvYNmuJi3KQmdWVk0q6G-Vu6aFq9gxJt5XSs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34398@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1068 bytes --]
New comment by tornaria on void-packages repository
https://github.com/void-linux/void-packages/pull/34398#issuecomment-986389904
Comment:
Note: this allows to use one of the standard mirrors since it expects the directory layout for different archs to be the same as the main repo. Implementing this would need more variables and IMO it would be a mess.
For more fine-grained control of the repos without disturbing the git worktree my suggestion would be to postpone the block
```
if [ -d $XBPS_DISTDIR/etc/xbps.d/custom ]; then
mkdir -p $confdir $crossconfdir
cp -f $XBPS_DISTDIR/etc/xbps.d/custom/*.conf $confdir
cp -f $XBPS_DISTDIR/etc/xbps.d/custom/*.conf $crossconfdir
fi
```
to later, right before the line `# Copy xbps repository keys to the masterdir.`
In this way the all the conf files (`20-repository-remote.conf`, etc) will be generated first, and then we get a chance to overwrite them with custom files. Right now is the other way around and there's no way to eliminate the configuration in these files.
next prev parent reply other threads:[~2021-12-06 2:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 0:48 [PR PATCH] " tornaria
2021-12-06 2:39 ` [PR PATCH] [Updated] " tornaria
2021-12-06 2:41 ` tornaria
2021-12-06 2:52 ` tornaria [this message]
2021-12-22 22:12 ` [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=20211206025215.VKjObRhEvYNmuJi3KQmdWVk0q6G-Vu6aFq9gxJt5XSs@z \
--to=tornaria@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).