dear fred,
i understand this is the dev mailing list and politeness does not supersede
correctness given the topical nature of this mailing list.
i am the last one to be pedantic, but serge *did* qualify his statement with a
“should” (i.e. expectation), meaning it was not absolute.
let us not
On Sun, 17 Mar 2024, Sergio Had wrote:
I have no idea what is going on with archaic versions, but Ruby 3.1+
through ruby-devel (3.4) should work on every system.
Please stop posting falsehoods. Ruby 3.1-3.3 most certainly do *not* work
on every system (yet), and I posted a list of the
I will investigate it. I’m in the middle of some *really* busy time at
work, so it will probably be a couple of months (I’ll set myself a reminder
for mid-May, but it’s more likely to be mid-June before I can start), and
it will take some time for me to get up to speed with the Ruby pg and look
at
> On Mar 17, 2024, at 6:09 AM, Austin Ziegler wrote:
> I reiterate that Ruby application ports (like sup or t) should *probably* be
> set up more like Go or Rust ports and that a tool like `go2port` or
> `cargo2port` (`gemspec2port, bundler2port`) which ultimately downloads the
> gemfiles and
On Sat, Mar 16, 2024 at 3:29 PM Sergio Had wrote:
> On Mar 17, 2024, at 12:57 AM, Austin Ziegler wrote:
> I am most definitely a Ruby expert, but I have yet to run any version of
> Ruby from MacPorts (because I use `ruby-build` and `mise` to build versions
> of Ruby that I require), and I
> On Mar 17, 2024, at 12:57 AM, Austin Ziegler wrote:
>
> I am most definitely a Ruby expert, but I have yet to run any version of Ruby
> from MacPorts (because I use `ruby-build` and `mise` to build versions of
> Ruby that I require), and I almost exclusively install Ruby packages via `gem
I am most definitely a Ruby expert, but I have yet to run any version of
Ruby from MacPorts (because I use `ruby-build` and `mise` to build versions
of Ruby that I require), and I almost exclusively install Ruby packages via
`gem install`.
I have *not* looked at the Ruby pg or many of the Ruby
Any Ruby experts among us?
Some Ruby ports hardcode versions for dependencies in a form restricting those
to a given major or minor version. Since many Ruby gems are not updated for
years (but still required for other stuff), this presents a problem: any
dependency using those will build but
