[MacPorts] #39471: rb-rubygems @1.3.7_1 gem1.8 symlinked to missing file
MacPorts
noreply at macports.org
Wed Jun 19 02:23:08 PDT 2013
#39471: rb-rubygems @1.3.7_1 gem1.8 symlinked to missing file
--------------------------------+--------------------------------
Reporter: matthew-macports@… | Owner: macports-tickets@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.1.3
Keywords: ruby gems gem | Port: rb-rubygems
--------------------------------+--------------------------------
Installing rb-rubygems using `sudo port install rb-rubygems` on my machine
creates a symlink `/opt/local/bin/gem-1.8` to the nonexistent file
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports
.org_release_tarballs_ports_ruby_rb-rubygems/rb-
rubygems/work/destroot//opt/local/libexec/ruby1.8/gem`
If I understand this right, it should be a symlink to
`/opt/local/libexec/ruby1.8/gem` but the symlink has been created with the
staging destroot included. Looking at the rb-rubygems Portfile, in `post-
destroot` it does:
`ln -s ${destroot}/${ruby.bindir}/gem
${destroot}${prefix}/bin/gem${ruby.link_binaries_suffix}`
I guess this should be:
`ln -s ${prefix}/${ruby.bindir}/gem
${destroot}${prefix}/bin/gem${ruby.link_binaries_suffix}`
...so that when it is installed from `${destroot}` to `${prefix}` it
points at where the binary will be. Or, if symlink rewriting is meant to
happen, it doesn't appear to be doing so here for some reason.
--
Ticket URL: <https://trac.macports.org/ticket/39471>
MacPorts <http://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list