You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
if I am not mistaken the ruby-keychain dependency is not supposed to be installed (because not necessary/sensible) on Linux, is it?
When I install keyring (version 0.4.1) on my Linux (elementary OS Juno - based on ubuntu 18.04) with gem install (within rvm) it installs the ruby-keychain dependency.
$ gem install -V keyring
[...]
Successfully installed ruby-keychain-0.3.2
[...]
Building native extensions. This could take a while...
[...]
*linux: installing gir_ffi-gnome_keyring...
[...]
Successfully installed keyring-0.4.1
$ gem list -l key
*** LOCAL GEMS ***
gir_ffi-gnome_keyring (0.0.10)
keyring (0.4.1)
ruby-keychain (0.3.2)
It's not a big deal because (at least after installing the libgnome-keyring-dev libgirepository1.0-dev packages) the Gem works fine (with the Gnome keyring) but the commit(s) in 0.4.1 sound like the dependencies should be handled for the different platforms separately.
The text was updated successfully, but these errors were encountered:
This is because the gemspec uses a runtime check but only the result of that check as run on the maintainer's machine is included in the final gem. It seems the maintainer uses a Mac.
Hi,
if I am not mistaken the
ruby-keychain
dependency is not supposed to be installed (because not necessary/sensible) on Linux, is it?When I install
keyring
(version 0.4.1) on my Linux (elementary OS Juno - based on ubuntu 18.04) withgem install
(withinrvm
) it installs theruby-keychain
dependency.The
gem dependency
command also lists it:As well as the website on rubygems.org: https://rubygems.org/gems/keyring/versions/0.4.1
It's not a big deal because (at least after installing the
libgnome-keyring-dev libgirepository1.0-dev
packages) the Gem works fine (with the Gnome keyring) but the commit(s) in 0.4.1 sound like the dependencies should be handled for the different platforms separately.The text was updated successfully, but these errors were encountered: