Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 13 Oct 2021 14:02:24 +0000
From:      bugzilla-noreply@freebsd.org
To:        ruby@FreeBSD.org
Subject:   [Bug 258108] devel/ruby-gems: Update to 3.2.26 (Fixes for Ruby 3.0)
Message-ID:  <bug-258108-21402-xbpo8DjW8u@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-258108-21402@https.bugs.freebsd.org/bugzilla/>
References:  <bug-258108-21402@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D258108

--- Comment #10 from Thibault Jouan <tj+freebsd_ports@a13.fr> ---
Created attachment 228667
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D228667&action=
=3Dedit
Workaround broken --destdir with bundler

(In reply to Yasuhiro Kimura from comment #8)=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
> The second one is that since 3.1 --destdir option of setup.rb has been br=
oken.  \ There are two report about it on upstream repository in GitHub.
>=C2=B7=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
> https://github.com/rubygems/rubygems/pull/2768=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20
> https://github.com/rubygems/rubygems/issues/3604=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20
>=C2=B7=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
> To make --destdir option work correctly both need to be fixed.=20=20=20=
=20=20=20=20

  I looked into it, but only for a very short time. If I recall=20=20=20=20=
=20=20=20=20
correctly, the new attached patch fix the "duplicated" dest dir in one=20
of the paths, but there was a third dest dir issue in addition to=20=20=20=
=20=20=20
those two already reported.=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20

  Also, I'm worried that even if it get fixed, it will break shortly=20=20=
=20
after (it happened multiple times in the past already, still for=20=20=20=
=20=20=20=20
`--destdir' option. Some people (myself included) trying to fix it=20=20=20=
=20=20
upstream in the past seems to have given up and now prefer to patch=20=20=
=20=20
their port directly (especially because they don't have to support=20=20=20=
=20=20
Windows too in this case).

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-258108-21402-xbpo8DjW8u>