Hi,
I’ve updated to macOS 14, installed MacPorts 2.8.1 for Sonoma and then upgraded
my ports. I noticed that ports that use ‘platform { darwin any }’ get
reinstalled during this process, and ‘port outdated’ shows ‘(platform darwin 22
≠ 23)’. Does MacPorts really need to reinstall these ports if
Nils,
> On 27 Sep 2023, at 12:42, Nils Breunese wrote:
>
> Hi,
>
> I’ve updated to macOS 14, installed MacPorts 2.8.1 for Sonoma and then
> upgraded my ports. I noticed that ports that use ‘platform { darwin any }’
> get reinstalled during this process, and ‘port outdated’ shows ‘(platform
>
That just means they are *supported* on any drawn version. Each version still
have its own build.
b.t.w. When upgrading to a new major OS version, you anyway should follow the
migration instructions, which involves manually removing all ports anyway.
https://trac.macports.org/wiki/Migration
On Sep 27, 2023, at 05:57, Nils Breunese wrote:
>
> I noticed that ports that use ‘platform { darwin any }’ get reinstalled
> during this process, and ‘port outdated’ shows ‘(platform darwin 22 ≠ 23)’.
> Does MacPorts really need to reinstall these ports if they’re marked as being
> suitable fo
On Sep 27, 2023, at 06:09, Christopher Jones wrote:
>
> That just means they are *supported* on any drawn version. Each version
> still have its own build.
But that's just what "any" means: they build identically on any OS version.
That's why only one single archive gets produced for these por
> On 27 Sep 2023, at 12:32 pm, Ryan Schmidt wrote:
>
> On Sep 27, 2023, at 06:09, Christopher Jones wrote:
>>
>> That just means they are *supported* on any drawn version. Each version
>> still have its own build.
>
> But that's just what "any" means: they build identically on any OS versi
Ryan Schmidt wrote:
> On Sep 27, 2023, at 06:09, Christopher Jones wrote:
>
>> b.t.w. When upgrading to a new major OS version, you anyway should follow
>> the migration instructions, which involves manually removing all ports
>> anyway.
>
> We do recommend that, but the piecemeal method Nils
Christopher Jones wrote:
> I had no idea we supported single tarballs for multiple OS versions.
>
> I must say, the distinction between
>
> platforms { darwin any }
>
> and
>
> platforms {darwin >= 11}
>
> which *does* result in specific tarballs for each OS is a bit too subtle for
> my ta
On 27/9/2023 20:42, Nils Breunese wrote:
Hi,
I’ve updated to macOS 14, installed MacPorts 2.8.1 for Sonoma and then upgraded
my ports. I noticed that ports that use ‘platform { darwin any }’ get
reinstalled during this process, and ‘port outdated’ shows ‘(platform darwin 22
≠ 23)’. Does MacPo
> On 27 Sep 2023, at 2:01 pm, Nils Breunese wrote:
>
> Christopher Jones wrote:
>
>> I had no idea we supported single tarballs for multiple OS versions.
>>
>> I must say, the distinction between
>>
>> platforms { darwin any }
>>
>> and
>>
>> platforms {darwin >= 11}
>>
>> which *does*
On 27/9/2023 23:01, Nils Breunese wrote:
Christopher Jones wrote:
I had no idea we supported single tarballs for multiple OS versions.
I must say, the distinction between
platforms { darwin any }
and
platforms {darwin >= 11}
which *does* result in specific tarballs for each OS is a bit to
Ryan Schmidt wrote:
> On Sep 27, 2023, at 05:57, Nils Breunese wrote:
>>
>> I noticed that ports that use ‘platform { darwin any }’ get reinstalled
>> during this process, and ‘port outdated’ shows ‘(platform darwin 22 ≠ 23)’.
>> Does MacPorts really need to reinstall these ports if they’re ma
Joshua Root wrote:
> On 27/9/2023 23:01, Nils Breunese wrote:
>
>> You can do this:
>> platforms { darwin any } { darwin >= 11 }
>> Which means that the port will install on Darwin 11+, and it will install
>> identically on all of those supported versions.
>
> Or the simpler form
>
> pla
On 27/9/2023 21:47, Christopher Jones wrote:
Is the logic behind what all the various options we can now use with platforms
documented somewhere ?
It's documented in the Guide.
- Josh
14 matches
Mail list logo
