diff options
| author | Danilo M. <danix@danix.xyz> | 2026-08-07 09:57:11 +0200 |
|---|---|---|
| committer | Danilo M. <danix@danix.xyz> | 2026-08-07 09:57:11 +0200 |
| commit | 78d37fb4f2f09de3900a120e3e11479c19b14d12 (patch) | |
| tree | 9c9ebe087c6a0b8f49be2a7d00f9e16c420574cd /network/metasploit-framework-bin/msfvenom.1 | |
| parent | 314bdb73f18db3670734e85f2ecfb176d8eb9612 (diff) | |
| download | sbo-slackbuilds-78d37fb4f2f09de3900a120e3e11479c19b14d12.tar.gz sbo-slackbuilds-78d37fb4f2f09de3900a120e3e11479c19b14d12.zip | |
CLAUDE.md: fix msf completion regen, gem paths are mandatory
The extract-to-tmp generator command as documented never worked on its
own. The embedded ruby has /opt/metasploit-framework baked in as its
prefix, so bundler resolves gems there regardless of the extract dir and
fails with Bundler::GemNotFound. It only appeared to work when a host
install sat at that path, which also meant it read the installed version
rather than the one being packaged.
Add the required GEM_HOME/GEM_PATH/BUNDLE_GEMFILE, note that the ruby
version in the gem path moves on upstream bumps, and drop the advice to
fall back to a live /opt install.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Diffstat (limited to 'network/metasploit-framework-bin/msfvenom.1')
0 files changed, 0 insertions, 0 deletions