Using cygport-0.36.9-1 with this patch merged in, it was confirmed that a ruby-3.3.1 package could be created in the local development environment.
Thank you for merging. On Mon, May 6, 2024 at 11:12 PM Jon Turney <jon.tur...@dronecode.org.uk> wrote: > > On 03/04/2024 15:18, Daisuke Fujimura via Cygwin-apps wrote: > > Thank you for reviewing this. > > > >> Can you clarify what the "failure" is here? > > > [...] > > > > /usr/share/rubygems/rubygems.rb:8:in `require': cannot load such file > > -- rbconfig (LoadError) > > > [...] > > Thanks very much for the detailed explanation. > > So this is an error (or warning?) generated by invoking the > not-yet-properly installed, just-built ruby in ${D}. > > I applied your patch. > > > On Sun, Mar 10, 2024 at 10:34 PM Jon Turney <jon.tur...@dronecode.org.uk> > > wrote: > >> > >> On 16/02/2024 12:51, Daisuke Fujimura via Cygwin-apps wrote: > >>> Attempting to create a package for ruby-3.3, but it fails when trying > >>> to detect a dependency on itself. > >> > >> Thanks for this patch. > >> > >> Can you clarify what the "failure" is here? > >> > >>> To avoid this, skip them if the target is `ruby`. > >> > >> The second hunk seems like a removes the dependency on ruby_xy for the > >> ruby package, which also provides ruby_xy. > >> > >> Historically, we've allowed self-dependencies like this, because they > >> seem to be benign, although it seems like we could do with some generic > >> code to suppress them > > ... except I added something to generically prevent a packages provides: > appearing it it's requires: >