From: "Patrice Clement" <monsieurp@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gentoo-bashcomp:master commit in: helpers/
Date: Tue, 16 Nov 2021 16:08:55 +0000 (UTC) [thread overview]
Message-ID: <1637078903.f3f401b1166bb3d7f79b9f3cb8ebfc3527cd4394.monsieurp@gentoo> (raw)
commit: f3f401b1166bb3d7f79b9f3cb8ebfc3527cd4394
Author: redneb <redneb <AT> gmx <DOT> com>
AuthorDate: Tue Nov 16 15:42:15 2021 +0000
Commit: Patrice Clement <monsieurp <AT> gentoo <DOT> org>
CommitDate: Tue Nov 16 16:08:23 2021 +0000
URL: https://gitweb.gentoo.org/proj/gentoo-bashcomp.git/commit/?id=f3f401b1
ignore non conf files in /etc/portage/repos.conf.
portage ignores any file in /etc/portage/repos.conf/ (when that is in
fact a directory) that does not have a name of the form "*.conf".
gentoo-bashcomp should emulate the behavior of portage. Otherwise you
might run into issues: e.g. if there is a backup of eselect-repo.conf
called eselect-repo.conf~ that contains references to a now removed
overlay, gentoo-bashcomp should not try to search for completions in the
now nonexistent repo directory
Closes: https://github.com/gentoo/gentoo-bashcomp/pull/5
Signed-off-by: Patrice Clement <monsieurp <AT> gentoo.org>
helpers/gentoo-common.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/helpers/gentoo-common.sh b/helpers/gentoo-common.sh
index 6e8d51c..9424ad6 100644
--- a/helpers/gentoo-common.sh
+++ b/helpers/gentoo-common.sh
@@ -7,7 +7,7 @@
# Retrieve PORTDIR/PORTDIR_OVERLAY location.
#
# In order of highest to lowest priority:
-# /etc/portage/repos.conf{,/*}
+# /etc/portage/repos.conf{,/*.conf}
# /usr/share/portage/config/repos.conf
# /etc/portage/make.conf
# /etc/make.conf
@@ -65,7 +65,7 @@ _parsereposconf() {
for f in @GENTOO_PORTAGE_EPREFIX@/usr/share/portage/config/repos.conf \
@GENTOO_PORTAGE_EPREFIX@/etc/portage/repos.conf \
- @GENTOO_PORTAGE_EPREFIX@/etc/portage/repos.conf/*; do
+ @GENTOO_PORTAGE_EPREFIX@/etc/portage/repos.conf/*.conf; do
[[ -f ${f} ]] || continue
insection=0
next reply other threads:[~2021-11-16 16:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 16:08 Patrice Clement [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-21 7:34 [gentoo-commits] proj/gentoo-bashcomp:master commit in: helpers/ Sam James
2023-01-14 16:39 Sam James
2023-01-14 16:39 Sam James
2019-02-10 23:04 Patrice Clement
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=1637078903.f3f401b1166bb3d7f79b9f3cb8ebfc3527cd4394.monsieurp@gentoo \
--to=monsieurp@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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