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
{{ message }}
Repository navigation
extconf.rb doesn't find libgit2 from GNU Guix #955
I am new to ruby, and actually just want to package this like the original poster, but from reading the sources of the two functions, neither dir_config nor pkg_config will set up anything but variables that will later be written to the Makefile.
Further more, while there is a check for pkg-config on the else half of the function, there is no check on the --use-system-libraries side.
I think what this code does, is extract the version of libgit2 that is bundled with rugged, and then check that the system libgit2 matches.
If the libgit2 tree has not been checked out it fails, despite the tree being used for nothing but extracting the major and minor version from version.h.
While I understand that it is inconvenient to have to update the version in extconf.rb manually, downloading an incomplete release (as the git submodule is missing), and then having to add the source from git just to compile against system libgit2 in the end, is also not a structurally sound path.
I'd also like to point out to you that the check would fail on your system, because rugged is developed against libgit2 head (no specific commit IDs are set anywhere that I could find), and thus seems to require 1.6.x.
Activity
chrschmidt commentedon Jun 5, 2023
I am new to ruby, and actually just want to package this like the original poster, but from reading the sources of the two functions, neither dir_config nor pkg_config will set up anything but variables that will later be written to the Makefile.
Further more, while there is a check for pkg-config on the else half of the function, there is no check on the --use-system-libraries side.
I think what this code does, is extract the version of libgit2 that is bundled with rugged, and then check that the system libgit2 matches.
If the libgit2 tree has not been checked out it fails, despite the tree being used for nothing but extracting the major and minor version from version.h.
While I understand that it is inconvenient to have to update the version in extconf.rb manually, downloading an incomplete release (as the git submodule is missing), and then having to add the source from git just to compile against system libgit2 in the end, is also not a structurally sound path.
chrschmidt commentedon Jun 5, 2023
I'd also like to point out to you that the check would fail on your system, because rugged is developed against libgit2 head (no specific commit IDs are set anywhere that I could find), and thus seems to require 1.6.x.