Bill Sommerfeld

> Isn't this (`-solaris2` instead of `-solaris2.11`) just a bug? For example [here](https://github.com/OpenIndiana/oi-userland/pull/15955/files#diff-b74acd4437e96a4cd20d99a585b5c509a4e0894e5580fa285aed700e0062b795R51)? If not, could you please share a pointer where this issue is visible? I'm asking because I...

> > > Isn't this (`-solaris2` instead of `-solaris2.11`) just a bug? For example [here](https://github.com/OpenIndiana/oi-userland/pull/15955/files#diff-b74acd4437e96a4cd20d99a585b5c509a4e0894e5580fa285aed700e0062b795R51)? If not, could you please share a pointer where this issue is visible? I'm asking...

currently on a brief vacation, will respond with a proposal next week.

now down to three main loose ends: 1) `_curses_panel` isn't being built; need to get to the bottom of why configure doesn't think it could work. 2) `08-py_db.patch` needs rework...

At this point, the one remaining loose end is `08-py_db.patch` which enables MDB python support (including `::pystack`); this is likely to be tricky as the interpreter structures used by this...

> Is there a reason that openssl1.1 needs to be used? Please consider changing "USE_OPENSSL11= yes" to 'OPENSSL_VERSION= 3.1" in the Makefile. Fixed as you suggested. I started with `python39/Makefile`,...

> FYI, there is `refresh-patches` make target. Done.

> I would not bother with `08-py_db.patch` unless it is easily portable from https://github.com/oracle/solaris-userland/blob/master/components/python/python311/patches/08-py_db.patch. If it is not portable then just add a note somewhere (in `Makefile` likely) so we...

> Once #16009 is merged please rebase on top of it and generate new sample-manifest. Done.

> What's wrong with pull requests? The fact that we don't accept pull requests isn't a statement that there's anything "wrong" with pull requests. We use a different process with...