Keeping in sync mingw-w64 in several Macs

[Ces VLC]

Nevermind, I found that this can be done creating packages from Macports
itself (with 'port mpkg'). Sorry for not having read the docs in depth!
BTW, this feature is great and I think I'm going to use it a lot. So that
rather than creating a custom Macports path for each package I build, I'll
just create a 'mypackages' path as the root for all of them.

César

On Thu, Mar 20, 2025 at 9:58 PM Ces VLC <cesarillovlc at gmail.com> wrote:

> Hi!
>
> I know Macports is designed for always having the latest version of every
> port in your Mac, but however there are sometimes in which I want to have
> exactly the same version of a port in all my Macs. One example is
> mingw-w64, because I want to be able to exactly reproduce same Windows
> executables no matter the Mac I'm using at the moment.
>
> The problem is that whenever I buy a new Mac, I cannot install in it the
> same Macports version that I have on an older Mac (and even if it was
> possible, I admit it might be unsafe, because the latest Mac I just got
> runs Sequoia, and my other Macs run older versions).
>
> However, I'd be happy even running a Intel binary of mingw-w64 that was
> compiled for an older MacOS, because even if it's Intel, it would run
> through Rosetta, and I'm fine with that. But, AFAIK, Macports doesn't let
> me "pack a binary" from one Mac and "unpack" it in another Mac. Or can it
> be done?
>
> I know that my best solution would be to build mingw-w64 myself, without
> Macports. That way I'd have total control over its binaries. But I'm always
> trying to avoid taking that direction, as it would need a lot of work and
> planning. So, if there's any way for achieving what I want with Macports,
> please tell!
>
> Thanks!
> César
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-users/attachments/20250320/4a748e1a/attachment.htm>