Hi all,
I’m trying to upgrade my port sigil (an epub editor) to the next major version
(see https://github.com/macports/macports-ports/pull/20359), and also use qt6
instead of qt5. Right now it builds fine, but will crash on launch
(SIGTRAP/SIGILL) because icudtl.dat is missing. qt5-qtwebengine
Niklas, you proposed that "proj9" be renamed to "proj", later in the
migration. I suggest a minor change. Keep "proj9" unchanged, and make
"proj" an alias for proj9, or whatever the macports mechanism is for that.
This means that current ports that need "proj9" explicitly in some way,
remain unaf
Hi all!
Glad you took up this subject again. I have meant to return to this, but things
always come between.
Just to clarify, my main objective is to *rename* the existing proj ports and
the latest version would always be ‘proj’.
The ports that do not support the new 8+ API will still have its
I have obviously forgotten to try the new Proj with R ports back then, and
atm away from native PPC hardware; so from my side I would prefer not
moving to a newer Proj right-away.
Switching to explicit proj5 port should be perfectly fine, of course. (And
then R ports won’t prevent anything else fro
octave/octave-octproj works with proj >= 6.3.0
I just haven’t updated the Portfile to version 9.x, as there haven’t been any
upstream changes in a while.
> On Jun 8, 2023, at 2:54 PM, Nicklas Larsson via macports-dev
> wrote:
>
> Hello all,
>
>
> I'd like to propose to simplify the maintain
As a contributor to ncarg (proj5), I like this change. Currently there are
only 10 ports that depend on the traditional "proj" which is really proj5
under the hood. Collectively there are only 3 maintainers plus a few
nomaintainers, and Sergey has already approved for several of the R ports.
So
Kirill A. Korinsky het volgende geschreven:
> I've used osxphotos once or twice and willing to make a port file and take
> care of it.
>
> PR will be made tonight.
Ah, that would be great. Thanks, Kirill! I’ll keep an eye out for it.
Nils.
Joshua Root wrote:
> On 7/9/2023 16:03, Nils Breunese wrote:
>> Does someone here think MacPorts could install osxphotos without using an
>> intermediary package manager like pipx?
>
> Yes, it looks like it's a standard setuptools build system, so the python
> portgroup should handle it fine.
