Please don't send me an individual copy of emails; I am subscribed.
Dan Ritter <d...@randomstring.org> wrote: > debian-u...@howorth.org.uk wrote: > > Dan Ritter <d...@randomstring.org> wrote: > > > p...@ymail.ne.jp wrote: > > > > For dev stuff, for example, I have many versions of ruby > > > > installed in the system by rbenv. > > > > > > > > Since I often change default ruby in interactive shell, this may > > > > break the ruby for sysadmin job in crontab. What’s the solution > > > > for this? > > > > > > Everywhere it matters, set an explicit PATH at the beginning. > > > > > > There is no other solution. > > > > Err, I know nothing about the subject but that doesn't seem to > > correspond with what it says in the readme at > > https://github.com/rbenv/rbenv > > rbenv is a fancy way of setting the PATH. It changes out setting > the PATH directly for requiring you to set up a .ruby-version > file for every project. If you commit to it, it might be better > for you. If you don't, it's harder to debug what's going wrong. The point is that the OP said they were using rbenv, so that's what matters to them. That's what they've chosen. > In general, development environments might want multiple Ruby > versions but production should only have one. If the production > version isn't the one that Debian is currently shipping, the > Debian-shipped version shouldn't be installed at all. > > -dsr-
