Can you explain why you
were running `gem update --system`? The only reason I can think of is
the nag message asked you to. The only reason I can think of is
the nag message asked you to.
I prefer to have all the gems as updated as possible, particularly
bundler and running `doas gem update --system` will update bundler and
rubygems at once.
After running it, if I remove the package ruby, it present a warning:
File
/usr/local/lib/ruby/gems/3.2/specifications/default/bundler-2.4.1.gemspec
does not exist
But it will remove the other files.
I understand that in this moment there is not much advantge because to
udpate bundler I can run:
doas gem install bundler
So as you prefer is fine.
El 2023-02-13 00:20, Jeremy Evans escribió:
On 02/12 09:28, vtamara wrote:
One question about
El 2023-02-09 11:38, Jeremy Evans escribi??:
> * Change how gem update --system nag message is removed, which also
> prevents gem update --system from working (nobody using the OpenBSD
> package should use it).
I have been testing 3.2 long ago doing frequently doas gem update
--system
and I have not
noticed any issue, why to remove it?
My understanding is it modifies files the ruby-* package installs.
That
will prevent clean uninstalls of the package. Can you explain why you
were running `gem update --system`? The only reason I can think of is
the nag message asked you to.
Thanks,
Jeremy
--
Dios, gracias por tu amor infinito.
--
Vladimir Támara Patiño. http://vtamara.pasosdeJesus.org/
http://www.pasosdejesus.org/dominio_publico_colombia.html
