Philippe Bruhat (BooK)

I agree the current workflow is confusing, and leads to issues, like the fact that it is practically impossible to get an idea of how many people actually attended the...

Great work! I'm going to copy over your commits to a psgi branch over the main repo. Given I have been republishing some other commits, our branches will look like...

This issue can be closed, per cf9d355875f10c8cf849bbb2d24b6b7877ff0e8f.

Is `/usr/lib/sparcv9` needed anywhere? In that case, would a patch like the following (swapping the paths) be more suitable? ``` --- perl-5.38.2/hints/solaris_2.sh +++ perl-5.38.2/hints/solaris_2.sh @@ -607,7 +607,7 @@ EOM ;;...

> Curious to see what you've come up with. The repository is here: . I'd recommend looking at the test data to see the kind of transformation it does.

Also, before embarking on this journey, I _did_ look for prior art. It seems I wasn't looking hard enough, or using the wrong keywords.

And I just realized that my description is very confusing. :sweat_smile: This module is not about changing: `our $VERSION = 1.23;` into `our $VERSION = 1.24;` in random Perl files....

> The lhs doesn't become magic by concatenation of something that is. That would be very weird. Strings don't turn into objects by concatenation, nor do they somehow become tied...

> > I think the obviously correct name for this account would be PUMPKING. 🙂 > > :) But personally, I would rather we avoid that term, as (a) the...

There was also the discussion of automating the releases of `Module::CoreList`, so maybe `P5P`, `PORTERS`, or something more general would be better. Naming is hard, but also a later step,...