From: "Jay Faulkner" <jayf@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/claude-code/
Date: Wed, 08 Oct 2025 19:40:31 +0000 (UTC) [thread overview]
Message-ID: <1759952409.a92b9e1ffefad0b1145163f9e72361eeb505280e.jayf@gentoo> (raw)
commit: a92b9e1ffefad0b1145163f9e72361eeb505280e
Author: Jay Faulkner <jayf <AT> gentoo <DOT> org>
AuthorDate: Wed Oct 8 19:39:51 2025 +0000
Commit: Jay Faulkner <jayf <AT> gentoo <DOT> org>
CommitDate: Wed Oct 8 19:40:09 2025 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a92b9e1f
dev-util/claude-code: drop 1.0.128
Signed-off-by: Jay Faulkner <jayf <AT> gentoo.org>
dev-util/claude-code/Manifest | 1 -
dev-util/claude-code/claude-code-1.0.128.ebuild | 86 -------------------------
2 files changed, 87 deletions(-)
diff --git a/dev-util/claude-code/Manifest b/dev-util/claude-code/Manifest
index 063ef781fbf5..e9ce77dcaff6 100644
--- a/dev-util/claude-code/Manifest
+++ b/dev-util/claude-code/Manifest
@@ -1,2 +1 @@
-DIST claude-code-1.0.128.tgz 36011028 BLAKE2B b135f3674f6e42cfa699cbcf8528c745ce495865ab7a2f55d0e61d9e529981375394b0ba27951f751ec730b3cafc831a11e99ee94a4c618b1f4c6b033479944c SHA512 b948397053097de41eb50cc5c3be95a5bae8e83017b2dd8ba6ef1aa19591152a10558bb96520276c1a31696996fc88271d2a8822fb4cc330a8aa6700f63f6b35
DIST claude-code-2.0.10.tgz 36028531 BLAKE2B 2cdd31f21efbb62107d36b23a3d4b7f72d704fb08b7d7b19a8d9d9b3d7a744fa77ce3ae4243357152d7b8f00e8133bd7c1b3987ee14960bcf3d676415fdffc9e SHA512 cb607a396e4c9de598ab35aad0d6f3ce072c0ad2344bb73ffc80ede036339a41a0a444b7076685a66141f7032f02ec72eda3acd606a9dc322e7686da173b3e61
diff --git a/dev-util/claude-code/claude-code-1.0.128.ebuild b/dev-util/claude-code/claude-code-1.0.128.ebuild
deleted file mode 100644
index b70c2b00d449..000000000000
--- a/dev-util/claude-code/claude-code-1.0.128.ebuild
+++ /dev/null
@@ -1,86 +0,0 @@
-# Copyright 1999-2025 Gentoo Authors
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=8
-
-DESCRIPTION="Claude Code - an agentic coding tool by Anthropic"
-HOMEPAGE="https://www.anthropic.com/claude-code"
-SRC_URI="https://registry.npmjs.org/@anthropic-ai/claude-code/-/claude-code-${PV}.tgz"
-S="${WORKDIR}/package"
-
-# NOTE(JayF): claude-code is only usable via paid subscription and has a
-# clickthrough EULA-type license. Please see $HOMEPAGE for
-# full details.
-LICENSE="all-rights-reserved"
-SLOT="0"
-KEYWORDS="amd64"
-
-IUSE="jetbrains"
-RESTRICT="bindist strip"
-
-RDEPEND="
- >=net-libs/nodejs-18
- sys-apps/ripgrep
-"
-
-src_compile() {
- # Skip, nothing to compile here.
- :
-}
-
-src_install() {
- dodoc README.md LICENSE.md
-
- # We are using a strategy of "install everything that's left"
- # so removing these here will prevent duplicates in /opt/claude-code
- rm -f README.md LICENSE.md package.json || die
- # remove vendored ripgrep
- rm -rf vendor/ripgrep || die
-
- # Install extentions these under /opt, and let users configure their
- # IDEs appropriately if they have opted-into having them installed.
- # Normally I wouldn't allow a few megs of data to be USE-flag-toggled,
- # but removing these cuts the already-small package size in half, so
- # it seems worth it.
- use jetbrains || rm -r vendor/${PN}-jetbrains-plugin || die
-
- insinto /opt/${PN}
- doins -r ./*
- fperms a+x opt/claude-code/cli.js
-
- dodir /opt/bin
- dosym -r /opt/${PN}/cli.js /opt/bin/claude
-
- # https://bugs.gentoo.org/962002 indicates that Claude doesn't use
- # path to find the `rg` binary. Gross. So we symlink it into the place
- # they expect it to be. Thanks to Leo Douglas for the patch.
- if use amd64; then
- dodir /opt/${PN}/vendor/ripgrep/x64-linux
- dosym -r /usr/bin/rg /opt/${PN}/vendor/ripgrep/x64-linux/rg
- elif use arm64; then
- dodir /opt/{$PN}/vendor/ripgrep/arm64-linux
- dosym -r /usr/bin/rg /opt/${PN}/vendor/ripgrep/arm64-linux/rg
- fi
-
- insinto /etc/${PN}
- doins "${FILESDIR}/managed-settings.json"
-
- # nodejs defaults to disabling deprecation warnings when running code
- # from any path containing a node_modules directory. Since we're installing
- # outside of the realm of npm, explicitly pass an option to disable
- # deprecation warnings so it behaves the same as it does if installed via
- # npm. It's proprietary; not like Gentoo users can fix the warnings anyway.
- sed -i 's/env node/env -S node --no-deprecation/' "${ED}/opt/claude-code/cli.js"
-}
-
-pkg_preinst() {
- if test -f "${ROOT}/etc/${PN}/policies.json"; then
- mv "${ROOT}/etc/${PN}/policies.json" "${ROOT}/etc/${PN}/managed-settings.json"
- fi
-}
-
-pkg_postinst() {
- elog "As of claude-code 1.0.110, the claude-code VSCode plugin was removed"
- elog "from the upstream npm package. Users previously using this bundled"
- elog "extension will have to source it elsewhere."
-}
next reply other threads:[~2025-10-08 19:40 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-08 19:40 Jay Faulkner [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-10-31 21:06 [gentoo-commits] repo/gentoo:master commit in: dev-util/claude-code/ Jay Faulkner
2025-10-28 19:32 Jay Faulkner
2025-10-27 17:32 Jay Faulkner
2025-10-21 22:38 Jay Faulkner
2025-10-21 16:41 Jay Faulkner
2025-10-13 16:47 Jay Faulkner
2025-10-08 19:40 Jay Faulkner
2025-10-05 19:56 Jay Faulkner
2025-10-03 18:18 Jay Faulkner
2025-09-30 19:59 Jay Faulkner
2025-09-29 21:14 Jay Faulkner
2025-09-24 22:54 Jay Faulkner
2025-09-19 16:46 Jay Faulkner
2025-09-17 16:00 Jay Faulkner
2025-09-16 15:14 Jay Faulkner
2025-09-15 17:07 Jay Faulkner
2025-09-12 18:38 Jay Faulkner
2025-09-11 15:33 Jay Faulkner
2025-09-10 15:06 Jay Faulkner
2025-09-09 22:08 Jay Faulkner
2025-09-08 14:39 Jay Faulkner
2025-09-05 18:34 Jay Faulkner
2025-09-04 17:40 Jay Faulkner
2025-09-03 22:07 Jay Faulkner
2025-09-02 17:16 Jay Faulkner
2025-08-28 15:51 Jay Faulkner
2025-08-26 15:20 Jay Faulkner
2025-08-26 15:20 Jay Faulkner
2025-08-25 15:48 Jay Faulkner
2025-08-25 15:48 Jay Faulkner
2025-08-25 15:48 Jay Faulkner
2025-08-23 3:24 Jay Faulkner
2025-08-23 3:24 Jay Faulkner
2025-08-22 16:32 Jay Faulkner
2025-08-22 16:32 Jay Faulkner
2025-08-20 14:57 Jay Faulkner
2025-08-20 14:57 Jay Faulkner
2025-08-17 4:22 Jay Faulkner
2025-08-17 1:03 Jay Faulkner
2025-08-16 23:34 Jay Faulkner
2025-08-16 23:34 Jay Faulkner
2025-08-15 17:44 Jay Faulkner
2025-08-15 17:44 Jay Faulkner
2025-08-12 22:44 Jay Faulkner
2025-08-12 22:44 Jay Faulkner
2025-08-11 16:35 Jay Faulkner
2025-08-11 16:35 Jay Faulkner
2025-08-07 20:06 Jay Faulkner
2025-08-07 20:06 Jay Faulkner
2025-07-12 22:12 Jay Faulkner
2025-07-06 20:00 Jay Faulkner
2025-07-06 20:00 Jay Faulkner
2025-07-06 20:00 Jay Faulkner
2025-06-28 17:17 Jay Faulkner
2025-06-26 20:30 Jay Faulkner
2025-06-26 20:30 Jay Faulkner
2025-06-20 19:52 Jay Faulkner
2025-06-20 19:52 Jay Faulkner
2025-06-19 3:23 Jay Faulkner
2025-06-19 3:22 Jay Faulkner
2025-06-18 21:58 Jay Faulkner
2025-06-18 21:58 Jay Faulkner
2025-06-18 21:58 Jay Faulkner
2025-06-17 22:33 Jay Faulkner
2025-06-17 15:55 Jay Faulkner
2025-06-17 15:55 Jay Faulkner
2025-06-13 21:00 Jay Faulkner
2025-06-13 21:00 Jay Faulkner
2025-06-12 18:54 Jay Faulkner
2025-06-12 18:54 Jay Faulkner
2025-06-10 20:18 Jay Faulkner
2025-06-10 20:18 Jay Faulkner
2025-06-09 17:01 Jay Faulkner
2025-06-09 17:01 Jay Faulkner
2025-06-04 18:40 Jay Faulkner
2025-06-04 18:40 Jay Faulkner
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=1759952409.a92b9e1ffefad0b1145163f9e72361eeb505280e.jayf@gentoo \
--to=jayf@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