<konsolebox>
Hello, is it universal to all installations of 3.1 that gem files no longer install executables to ~/.gem/ruby/VERSION/bin?
<ox1eef>
that'd only happen for --user-install afaik, or if you happen to be using a version manager that keeps the install local to $HOME
<konsolebox>
I don't use rvm in this case.
<konsolebox>
Gentoo ruby to be exact.
<konsolebox>
However I'm not sure if asking in #gentoo-ruby would be helpful.
<ox1eef>
it sounds like you expect --user-install behavior
<konsolebox>
If --user-install means installing in ~/.gem yes
<konsolebox>
But recent installation no longer install binaries in a common directory.
<konsolebox>
e.g. ~/.gem/ruby/3.0.0/bin/
<konsolebox>
Actually it's 3.1.0
<konsolebox>
bin directory itself no longer exists, so I'm wondering if rubygems has a new strategy again... perhaps avoid install binaries to common dir because of possible binary name conflicts.
<ox1eef>
that's what --user-install means, yep. so, where are they being installed instead?
<konsolebox>
Gems are still installed to ~/.gem/ruby/version, but none is being installed to bin.
<ox1eef>
sounds strange..
<konsolebox>
I'm wondering if there's a new strategy in 3.1.0 or maybe newer versions of rubygems.
<ox1eef>
are you sure it is not voodoo from the gentoo maintainers
<konsolebox>
Recently I notice rake remove bin/rake
<ox1eef>
i can tell you how 3.1 bins look for me, 1second
<konsolebox>
Thanks that would help.
<konsolebox>
There's no reason for Gentoo to alter the behavior though.
<ox1eef>
i built ruby myself, and installed it to : ~/.rubies/3.1.0/ and inside there, i see ~/.rubies/3.1.0/bin/, which has binstubs for installed gems.
<konsolebox>
Ok I'll try to install using rvm and see if it makes a difference. I'll also try to examine the changes in rubygems.
Dooky has quit [Ping timeout: 240 seconds]
<ox1eef>
there's no context with that commit, still i don't think the behavior of gem bins has changed, especially in teeny patches
<ox1eef>
it is also pretty easy to build from hand and since youre on gentoo i guess youre no stranger to that
<konsolebox>
Yes, but I prefer not having multiple installed ruby versions
<ox1eef>
my strategy is to build by hand, and use chruby to manage switching between them.
<konsolebox>
I mean I don't want to have a ruby that's only available to the user, and another one that's system
<ox1eef>
ah i see, then you are using rvm for every user - that works, i cant say id approach the problem with rvm though, id prefer something like chruby
<konsolebox>
No I'll actually try rvm in ubuntu which is in my other machine. I'll see if it works there.
<ox1eef>
cool
<konsolebox>
I don't install rvm in Gentoo
sympt has joined #ruby
oxfuxxx has joined #ruby
sympt has quit [Remote host closed the connection]
konsolebox has quit [Remote host closed the connection]
konsolebox has joined #ruby
konsolebox has quit [Client Quit]
r3m has joined #ruby
summerisle is now known as eof
oxfuxxx has quit [Ping timeout: 246 seconds]
oxfuxxx has joined #ruby
Dooky has joined #ruby
Dooky has quit [Ping timeout: 260 seconds]
Ziyan has joined #ruby
mixfix41 has joined #ruby
Dooky has joined #ruby
rahl has quit [Ping timeout: 240 seconds]
oxfuxxx has quit [Ping timeout: 252 seconds]
oxfuxxx has joined #ruby
mixfix41 has quit [Read error: Connection reset by peer]
konsolebox has joined #ruby
<konsolebox>
ox1eef: I found out it was a Gentoo issue and I'm asking now why. It's likely an overlook.
<ox1eef>
ok cool
oxfuxxx has quit [Ping timeout: 240 seconds]
oxfuxxx has joined #ruby
oxfuxxx has quit [Ping timeout: 240 seconds]
sympt has joined #ruby
sympt has quit [Remote host closed the connection]
sympt has joined #ruby
ur5us has quit [Ping timeout: 260 seconds]
ssh0732 has joined #ruby
ssh073 has quit [Ping timeout: 240 seconds]
ssh0732 is now known as ssh073
gigamo has quit [*.net *.split]
llua has quit [*.net *.split]
Artea has quit [*.net *.split]
Hobbyboy has quit [*.net *.split]
oz has quit [*.net *.split]
frodl has quit [*.net *.split]
dannyAAM has quit [*.net *.split]
BSaboia has quit [*.net *.split]
dostoyevsky2 has quit [*.net *.split]
dostoyevsky2 has joined #ruby
Artea has joined #ruby
frodl has joined #ruby
Hobbyboy has joined #ruby
gigamo has joined #ruby
BSaboia has joined #ruby
ox has joined #ruby
dannyAAM has joined #ruby
llua has joined #ruby
r0bby has quit [*.net *.split]
bhaak has quit [*.net *.split]
rubin55 has quit [*.net *.split]
josephl has quit [*.net *.split]
ox1eef has quit [*.net *.split]
josephl has joined #ruby
bhaak has joined #ruby
rubin55 has joined #ruby
ox1eef has joined #ruby
r0bby has joined #ruby
konsolebox has quit [Quit: Leaving]
Dooky has quit [Ping timeout: 240 seconds]
Vonter has quit [Read error: Connection reset by peer]
Vonter has joined #ruby
vigumnov has joined #ruby
victori has quit [Read error: Connection reset by peer]
Dooky has joined #ruby
ssh073 has quit [Ping timeout: 240 seconds]
protektwar has joined #ruby
protektwar has quit [Changing host]
protektwar has joined #ruby
teclator has joined #ruby
mixfix41 has joined #ruby
N_3Do has joined #ruby
<N_3Do>
how to set recursion limit of ruby
Dooky has quit [Ping timeout: 260 seconds]
Ziyan has quit [Ping timeout: 248 seconds]
___nick___ has joined #ruby
Ziyan has joined #ruby
N_3Do has quit [Ping timeout: 276 seconds]
N_3Do has joined #ruby
<ox1eef>
do you mean avoid it? RubyVM::InstructionSequence.compile_option = {tailcall_optimization: true}
<ox1eef>
test what the limit is, or if it is not hit, with def test(n = 0); print "n is ", n, "\n"; test(n + 1); end
Jonopoly has quit [Quit: WeeChat 3.0]
N_3Do has quit [Remote host closed the connection]
Dooky has joined #ruby
Dooky has quit [Ping timeout: 260 seconds]
dionysus69 has joined #ruby
schne1der has joined #ruby
Dooky has joined #ruby
jpn has joined #ruby
Ziyan has quit [Ping timeout: 246 seconds]
Ziyan has joined #ruby
ur5us has joined #ruby
Dooky has quit [Ping timeout: 276 seconds]
ur5us has quit [Remote host closed the connection]
ur5us has joined #ruby
gr33n7007h has quit [Ping timeout: 248 seconds]
gr33n7007h has joined #ruby
namkeleser has joined #ruby
ur5us has quit [Ping timeout: 248 seconds]
rapha has joined #ruby
<rapha>
hi all
<rapha>
how do people usually deal with factoring something out into a gem ... the nice part is, now you can keep working on your main project without seeing the gem's code all the time. but what if you need to work on the code some more that's now part of the gem. there's no `--editable` option like with Python's pip. can bundler help here, somehow?
Dooky has joined #ruby
<ox1eef>
rapha: one of the great things about ruby is that you can reopen classes, and modules, that allows you to extend the gem before moving the changes into the gem itself.
<rapha>
Sounds like twice the work for no real gain. If the code you'd like to change is not your own, sure, extend away. But I was hoping there'd be something more like pip's -e.
oxfuxxx has joined #ruby
<ox1eef>
that's by no means the only way, you can also use: gem "foobar", path: "../foobar" in either gem.deps.rb or a Gemfile. that way you can make local edits to the gem, and see them reflected in the code using the Gemfile / gem.deps.rb
oxfuxxx has quit [Remote host closed the connection]
ur5us has quit [Ping timeout: 240 seconds]
jpn has quit [Ping timeout: 252 seconds]
Dooky has quit [Ping timeout: 260 seconds]
<jhass[m]>
Finally you can consider spinning out your gem out of your main codebase/monorepo with git subtree
bit4bit has quit [Remote host closed the connection]
wand has quit [Remote host closed the connection]
wand has joined #ruby
RickHull has quit [Ping timeout: 248 seconds]
schne1der has quit [Ping timeout: 240 seconds]
dionysus69 has quit [Ping timeout: 276 seconds]
schne1der has joined #ruby
Spitfire has joined #ruby
jpn has quit [Ping timeout: 276 seconds]
dionysus69 has joined #ruby
Sankalp has quit [Ping timeout: 240 seconds]
Sankalp has joined #ruby
gigamo has quit [Changing host]
gigamo has joined #ruby
RickHull has joined #ruby
Common-Lisp has joined #ruby
Ziyan has quit [Ping timeout: 240 seconds]
Ziyan has joined #ruby
<rapha>
ah! these were the kinds of things i was looking for ... thank you both, ox1eef and jhass[m]!
<rapha>
i've read about git subtree when it was new but haven't used it so far. perhaps this is a good opportunity. although the path: method looks a little nicer somehow.