From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/ruby-scripts:master commit in: eselect-ruby/
Date: Sun, 8 Oct 2023 08:39:07 +0000 (UTC) [thread overview]
Message-ID: <1696754337.c717ca0b202a2480ac307b5ad09073e90d0145d7.graaff@gentoo> (raw)
commit: c717ca0b202a2480ac307b5ad09073e90d0145d7
Author: Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Sun Oct 8 08:15:27 2023 +0000
Commit: Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Sun Oct 8 08:38:57 2023 +0000
URL: https://gitweb.gentoo.org/proj/ruby-scripts.git/commit/?id=c717ca0b
eselect-ruby: stop managing irb
The irb code is spun off into a gem now (in dev-ruby/irb) and upstream
recommends to use this version with all ruby versions, rather than the
vendored version.
Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>
eselect-ruby/ruby.eselect | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/eselect-ruby/ruby.eselect b/eselect-ruby/ruby.eselect
index ef0fc1b..6b97f82 100644
--- a/eselect-ruby/ruby.eselect
+++ b/eselect-ruby/ruby.eselect
@@ -4,7 +4,7 @@
DESCRIPTION="Manage Ruby symlinks"
MAINTAINER="ruby@gentoo.org"
-VERSION="20230616"
+VERSION="20231008"
bindir=/usr/bin
libdir=/usr/lib
@@ -41,8 +41,8 @@ check_target() {
}
remove_symlinks() {
- rm -f ${EROOT}${bindir}/{ruby,gem,irb,erb,ri,rdoc} && \
- rm -f ${EROOT}${man1dir}/{ruby,irb,erb,ri}.1*
+ rm -f ${EROOT}${bindir}/{ruby,gem,erb,ri,rdoc} && \
+ rm -f ${EROOT}${man1dir}/{ruby,erb,ri}.1*
# Remove legacy testrb link if it still exists.
local testrb="${EROOT}${bindir}/testrb"
@@ -61,7 +61,7 @@ remove_symlinks() {
create_man_links() {
local version=${1}
- for manpage in "ruby" "irb" "erb" "ri" ; do
+ for manpage in "ruby" "erb" "ri" ; do
for m in ${EROOT}${man1dir}/${manpage}${version}.1* ; do
if [[ -e ${m} ]]; then
echo ".so ${manpage}${version}.1" > ${EROOT}${man1dir}/${manpage}.1 || \
@@ -78,7 +78,7 @@ create_symlinks() {
local path="${EROOT}${bindir}/"
# these have to work
- for f in "ruby" "irb" "erb" "ri" "rdoc" ; do
+ for f in "ruby" "erb" "ri" "rdoc" ; do
ln -s "${f}${version}" "${path}${f}" || \
die -q "Could not set ${f} symlink"
done
next reply other threads:[~2023-10-08 8:39 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-08 8:39 Hans de Graaff [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-25 5:41 [gentoo-commits] proj/ruby-scripts:master commit in: eselect-ruby/ Hans de Graaff
2023-12-26 8:24 Hans de Graaff
2023-08-13 6:41 Hans de Graaff
2023-08-13 6:41 Hans de Graaff
2023-04-09 7:37 Hans de Graaff
2022-03-13 7:11 Hans de Graaff
2020-12-25 8:01 Hans de Graaff
2019-12-22 9:05 Hans de Graaff
2019-01-21 18:36 Hans de Graaff
2018-12-25 6:28 Hans de Graaff
2017-12-25 7:33 Hans de Graaff
2017-12-25 7:33 Hans de Graaff
2017-07-23 7:46 Hans de Graaff
2017-07-23 7:46 Hans de Graaff
2017-07-23 7:46 Hans de Graaff
2016-12-26 16:38 Hans de Graaff
2015-12-29 10:56 Hans de Graaff
2015-12-29 10:39 Hans de Graaff
2014-12-27 19:07 Manuel Rüger
2013-12-27 7:35 Alex Legler
2013-08-14 12:04 Alex Legler
2013-08-14 12:04 Alex Legler
2013-08-14 12:04 Alex Legler
2013-08-14 12:04 Alex Legler
2012-01-05 21:47 Alex Legler
2011-03-06 15:28 Alex Legler
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=1696754337.c717ca0b202a2480ac307b5ad09073e90d0145d7.graaff@gentoo \
--to=graaff@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