Re: MacPorts XCode Installation

[Michele Venturi]

I have made a script to install the right version of Xcode

https://gist.github.com/dardo82/1a68666175e84ebfb3d03fc4b75a3609


It requires the xcodes command that can be found here

https://github.com/RobotsAndPencils/xcodes

Maybe it should be packaged as a new port,it is useful...

Accepting the license can also be automated if needed.

Il mar 8 mar 2022, 03:21 raf  ha scritto:

> On Tue, Mar 08, 2022 at 01:13:36PM +1100, macpo...@raf.org wrote:
>
> > > Il lun 7 mar 2022, 12:38 Ryan Schmidt  ha
> scritto:
> > >
> > > > On Feb 26, 2022, at 12:04, Haren Samarasinghe wrote:
> > > >
> > > > > After reading the installation guide [1], quite a few people that
> I've
> > > > introduced MacPorts to have thought that a full XCode installation is
> > > > required. They're uncertain of doing this due to the large amount of
> space
> > > > it requires.
> > > > >
> > > > > In reality, I'd say that the majority of ports only require the
> command
> > > > line tools. In the scenarios where XCode is required for a port, the
> user
> > > > is normally alerted to this.
> > > > >
> > > > > I was planning on changing the docs [1][2] to show that XCode isn't
> > > > required, but I wanted to first check whether this would be an
> acceptable
> > > > change.
> > > >
> > > > Yes that's a good idea.
> > > >
> > > > If the port you're installing (and its dependencies) are available as
> > > > binaries, you do not need Xcode and you do not need the command line
> tools.
> > > > MacPorts will just install the binaries. MacPorts will probably print
> > > > warnings about Xcode and/or CLT being missing but in this case they
> can be
> > > > ignored.
> > > >
> > > > If the port (or its dependencies) are not available as binaries,
> you'll
> > > > probably need either Xcode or the command line tools. If you don't
> have
> > > > them installed, you'll get warnings, and then probably a build
> failure.
> > > >
> > > > Some ports need Xcode to build. These are (hopefully) marked with
> > > > "use_xcode yes". If you try to install such a port and you do not
> have
> > > > Xcode installed, MacPorts will tell you to install it.
> >
> > On a related note, the other day I was on my brother's
> > 10.14 mac, and I needed to migrate its macports from
> > a version for 10.13. There are instructions at
> > https://guide.macports.org/#installing.xcode that say:
> >
> >   2.1.1. Install Xcode on OS X 10.9 or Later
> >   Download the latest version of Xcode from the Apple developer
> >   website or get it using the Mac App Store.
> >
> > But the latest version of XCode is incompatible with 10.14,
> > and the Mac App Store won't install it (or any other version).
> > So those instructions might need an update.
> >
> > https://trac.macports.org/wiki/Migration says:
> >
> >   Install the latest version of Xcode that is compatible with your OS.
> >   Open the Xcode application once after installation and follow any
> prompts.
> >
> > But it links to the page above, not to a page showing
> > the latest compatible versions of XCode for each macos
> > version.
> >
> > I'm sure I've seen such a list in the past, but can't
> > remember where it is, and I can't seem to find it today.
> > Is it somewhere prominent and I'm just not finding it?
> > It would be great if either of the above pages linked to it.
> >
> > Ah, this has a great compatibility chart:
> > https://en.wikipedia.org/wiki/Xcode#Xcode_11.x_(since_SwiftUI_framework)
> >
> > I know this thread is about letting people know that XCode
> > isn't always needed, but I think the instructions for getting
> > the right XCode for old macos systems could be better too.
> >
> > cheers,
> > raf
>
> I think is the page I originally saw:
>
>   https://xcodereleases.com/
>
> cheers,
> raf
>
>

Re: MacPorts XCode Installation

[raf]

On Tue, Mar 08, 2022 at 01:13:36PM +1100, macpo...@raf.org wrote:

> > Il lun 7 mar 2022, 12:38 Ryan Schmidt  ha scritto:
> > 
> > > On Feb 26, 2022, at 12:04, Haren Samarasinghe wrote:
> > >
> > > > After reading the installation guide [1], quite a few people that I've
> > > introduced MacPorts to have thought that a full XCode installation is
> > > required. They're uncertain of doing this due to the large amount of space
> > > it requires.
> > > >
> > > > In reality, I'd say that the majority of ports only require the command
> > > line tools. In the scenarios where XCode is required for a port, the user
> > > is normally alerted to this.
> > > >
> > > > I was planning on changing the docs [1][2] to show that XCode isn't
> > > required, but I wanted to first check whether this would be an acceptable
> > > change.
> > >
> > > Yes that's a good idea.
> > >
> > > If the port you're installing (and its dependencies) are available as
> > > binaries, you do not need Xcode and you do not need the command line 
> > > tools.
> > > MacPorts will just install the binaries. MacPorts will probably print
> > > warnings about Xcode and/or CLT being missing but in this case they can be
> > > ignored.
> > >
> > > If the port (or its dependencies) are not available as binaries, you'll
> > > probably need either Xcode or the command line tools. If you don't have
> > > them installed, you'll get warnings, and then probably a build failure.
> > >
> > > Some ports need Xcode to build. These are (hopefully) marked with
> > > "use_xcode yes". If you try to install such a port and you do not have
> > > Xcode installed, MacPorts will tell you to install it.
> 
> On a related note, the other day I was on my brother's
> 10.14 mac, and I needed to migrate its macports from
> a version for 10.13. There are instructions at
> https://guide.macports.org/#installing.xcode that say:
> 
>   2.1.1. Install Xcode on OS X 10.9 or Later
>   Download the latest version of Xcode from the Apple developer
>   website or get it using the Mac App Store.
> 
> But the latest version of XCode is incompatible with 10.14,
> and the Mac App Store won't install it (or any other version).
> So those instructions might need an update.
> 
> https://trac.macports.org/wiki/Migration says:
> 
>   Install the latest version of Xcode that is compatible with your OS.
>   Open the Xcode application once after installation and follow any prompts.
> 
> But it links to the page above, not to a page showing
> the latest compatible versions of XCode for each macos
> version.
> 
> I'm sure I've seen such a list in the past, but can't
> remember where it is, and I can't seem to find it today.
> Is it somewhere prominent and I'm just not finding it?
> It would be great if either of the above pages linked to it.
> 
> Ah, this has a great compatibility chart:
> https://en.wikipedia.org/wiki/Xcode#Xcode_11.x_(since_SwiftUI_framework)
> 
> I know this thread is about letting people know that XCode
> isn't always needed, but I think the instructions for getting
> the right XCode for old macos systems could be better too.
> 
> cheers,
> raf

I think is the page I originally saw:

  https://xcodereleases.com/

cheers,
raf

Re: MacPorts XCode Installation

[macports]

> Il lun 7 mar 2022, 12:38 Ryan Schmidt  ha scritto:
> 
> > On Feb 26, 2022, at 12:04, Haren Samarasinghe wrote:
> >
> > > After reading the installation guide [1], quite a few people that I've
> > introduced MacPorts to have thought that a full XCode installation is
> > required. They're uncertain of doing this due to the large amount of space
> > it requires.
> > >
> > > In reality, I'd say that the majority of ports only require the command
> > line tools. In the scenarios where XCode is required for a port, the user
> > is normally alerted to this.
> > >
> > > I was planning on changing the docs [1][2] to show that XCode isn't
> > required, but I wanted to first check whether this would be an acceptable
> > change.
> >
> > Yes that's a good idea.
> >
> > If the port you're installing (and its dependencies) are available as
> > binaries, you do not need Xcode and you do not need the command line tools.
> > MacPorts will just install the binaries. MacPorts will probably print
> > warnings about Xcode and/or CLT being missing but in this case they can be
> > ignored.
> >
> > If the port (or its dependencies) are not available as binaries, you'll
> > probably need either Xcode or the command line tools. If you don't have
> > them installed, you'll get warnings, and then probably a build failure.
> >
> > Some ports need Xcode to build. These are (hopefully) marked with
> > "use_xcode yes". If you try to install such a port and you do not have
> > Xcode installed, MacPorts will tell you to install it.

On a related note, the other day I was on my brother's
10.14 mac, and I needed to migrate its macports from
a version for 10.13. There are instructions at
https://guide.macports.org/#installing.xcode that say:

  2.1.1. Install Xcode on OS X 10.9 or Later
  Download the latest version of Xcode from the Apple developer
  website or get it using the Mac App Store.

But the latest version of XCode is incompatible with 10.14,
and the Mac App Store won't install it (or any other version).
So those instructions might need an update.

https://trac.macports.org/wiki/Migration says:

  Install the latest version of Xcode that is compatible with your OS.
  Open the Xcode application once after installation and follow any prompts.

But it links to the page above, not to a page showing
the latest compatible versions of XCode for each macos
version.

I'm sure I've seen such a list in the past, but can't
remember where it is, and I can't seem to find it today.
Is it somewhere prominent and I'm just not finding it?
It would be great if either of the above pages linked to it.

Ah, this has a great compatibility chart:
https://en.wikipedia.org/wiki/Xcode#Xcode_11.x_(since_SwiftUI_framework)

I know this thread is about letting people know that XCode
isn't always needed, but I think the instructions for getting
the right XCode for old macos systems could be better too.

cheers,
raf

Re: Fwd: rsync build failure on mojave

[Dave Horsfall]

On Mon, 7 Mar 2022, Ryan Schmidt wrote:

> https://trac.macports.org/wiki/BadContent

A fine collection of perps :-)  I haven't seen any of them though, as I 
make extensive use of DNSBLs[*], but that's not to everyone's taste.

[*]
http://www.horsfall.org/spam.html (I don't run HTTPS yet)
https://en.wikipedia.org/wiki/Domain_Name_System-based_blackhole_list

-- Dave

Re: Running a mail server via MacPorts on macOS Monterey

[Gerben Wierda via macports-users]

I don’t, I did not find a way to do OD authentication from dovecot (and postfix 
relies on dovecot). I’d like to do that, though there is a disadvantage too in 
my case (solvable).

Gerben Wierda (LinkedIn )
R IT Strategy  (main site)
Book: Chess and the Art of Enterprise Architecture 
Book: Mastering ArchiMate 

> On 7 Mar 2022, at 14:33, Ben Greenfield via macports-users 
>  wrote:
> 
> Thanks for this outline. This has been on my todo list for a couple of years
> 
> I imagine you are using the host system’s Open Directory directory for 
> authentication.
> 
> Thanks,
> 
> Ben
> 
> 
> 
>> On Mar 4, 2022, at 7:12 PM, Steve Wardle via macports-users 
>> > > wrote:
>> 
>> I initially replied to Gerben off list but I am running my mail server on 
>> macOS 12.2.1.
>> 
>> Using macports packages for:
>>  postfix +dovecot_sasl +ldap +pcre +smtputf8 +tls
>>  amavisd-new
>>  clamav
>>  dovecot
>>  libmilter
>>  unbound +libevent
>>  certbot
>> 
>> Installing / building from source:
>>  opendkim
>>  opendmarc
>>  policyd-spf
>>  postfwd
>>  postwhite
>>  sshguard
>> 
>> Steve
>> 
>>> On 3 Mar 2022, at 13:38, Gerben Wierda via macports-users 
>>> >> > wrote:
>>> 
>>> Apart from Steven Smith, are there other users here that run a mail server 
>>> setup via MacPorts? And is already someone else running on Monterey?
>>> 
>>> I am and I’d like to link up to compare the situations, issues, etc. 
>>> 
>>> Gerben Wierda (LinkedIn )
>>> R IT Strategy  (main site)
>>> Book: Chess and the Art of Enterprise Architecture 
>>> 
>>> Book: Mastering ArchiMate 
>>> 
>> 
> 

Re: MacPorts XCode Installation

[Michele Venturi]

I've filed a new ticket, is it ok?
https://trac.macports.org/ticket/64777


Michele Venturi
about.me/dardo82



Il giorno lun 7 mar 2022 alle ore 17:51 Chris Jones <
jon...@hep.phy.cam.ac.uk> ha scritto:

>
> whatever you think relevant, from the discussion here. If its not clear
> it can be added to later on so don't worry about including everything at
> first. But please lets have the discussion in trac rather than here...
>
> On 07/03/2022 4:28 pm, Michele Venturi wrote:
> > What should I include in the bug report to make it clear?
> >
> > Il lun 7 mar 2022, 17:25 Marius Schamschula  > > ha scritto:
> >
> > Michele,
> >
> > Please submit a MacPorts ticket!
> >
> > Other users may search trac if they encounter the same issue. We can
> > also link to any upstream tickets from there.
> >
> >> On Mar 7, 2022, at 10:22 AM, Michele Venturi  >> > wrote:
> >>
> >> Should I submit a bug report before we even know if it's a
> >> MacPorts specific issue? Or how do we find that out?
> >>
> >> Il lun 7 mar 2022, 16:47 Chris Jones  >> > ha scritto:
> >>
> >>
> >>
> >> On 07/03/2022 3:31 pm, Michele Venturi wrote:
> >> > I have the required libraries in /usr/lib/swift too,but MPV
> >> is looking
> >> > for them in /opt/local/lib,so it doesn't find them:
> >> >
> >> > otool -l $(which mpv)
> >> > ...
> >> > cmd LC_RPATH
> >> > cmdsize 32
> >> > path /opt/local/lib (offset 12)
> >> >
> >> > Should we change RPATH or add symbolic links?
> >>
> >> No, those are not the solutions here. If there is an issue
> >> with the
> >> build on 10.13 we should fix that instead, rather than apply
> >> after-the-fact bandaids.
> >>
> >> The first thing to determine is if its a MacPorts specific
> >> issue due to
> >> how the build is performed, or an upstream issue. Either way
> >> please
> >> submit a bug report to macports trac so the discussion on this
> >> can
> >> continue there.
> >>
> >> Chris
> >>
> >> >
> >> > Michele Venturi
> >> > about.me/dardo82 
> >> >
> >> >
> >> >
> >> <
> https://about.me/dardo82?promo=email_sig_source=product_medium=email_sig_campaign=gmail_api_content=thumb
> >> <
> https://about.me/dardo82?promo=email_sig_source=product_medium=email_sig_campaign=gmail_api_content=thumb
> >>
> >>
> >> >
> >> > Michele Venturi
> >> > about.me/dardo82 
> >> >
> >> <
> https://about.me/dardo82?promo=email_sig_source=product_medium=email_sig_campaign=gmail_api_content=thumb
> >> <
> https://about.me/dardo82?promo=email_sig_source=product_medium=email_sig_campaign=gmail_api_content=thumb
> >>
> >>
> >> >
> >> >
> >> >
> >> >
> >> > Il giorno lun 7 mar 2022 alle ore 15:46 Ryan Schmidt
> >> > mailto:ryandes...@macports.org>
> >>  >> >> ha scritto:
> >> >
> >> >
> >> >
> >> > On Mar 7, 2022, at 08:34, Michele Venturi wrote:
> >> >
> >> >  > If I install MPV without Xcode I get an error when I
> >> launch it:
> >> >  >
> >> >  > dyld: Library not loaded:
> >> @rpath/libswiftAVFoundation.dylib
> >> >  >   Referenced from: /opt/local/bin/mpv
> >> >  >   Reason: image not found
> >> >  >
> >> >  > It's missing something,have you tried to execute it
> >> on 10.13?
> >> >
> >> > I have not.
> >> >
> >> > I guess you're right, in relation to the Swift language
> >> usage I
> >> > mentioned earlier, this port does appear to need
> >> > libswiftAVFoundation.dylib at runtime. And maybe it is
> >> expecting to
> >> > find it within Xcode on your system. (It depends on what
> >> @rpath
> >> > expands to. I forget what the command is to interrogate
> >> a binary
> >> > about its rpaths.)
> >> >
> >> > Swift is still a new programming language and I don't
> >> think we have
> >> > many ports in MacPorts that use Swift so I'm not sure if
> >> this should
> >> > be considered normal or not.
> >> >
> >> > I see that I have 

Re: MacPorts XCode Installation

[Chris Jones]

whatever you think relevant, from the discussion here. If its not clear 
it can be added to later on so don't worry about including everything at 
first. But please lets have the discussion in trac rather than here...


On 07/03/2022 4:28 pm, Michele Venturi wrote:

What should I include in the bug report to make it clear?

Il lun 7 mar 2022, 17:25 Marius Schamschula > ha scritto:


Michele,

Please submit a MacPorts ticket!

Other users may search trac if they encounter the same issue. We can
also link to any upstream tickets from there.


On Mar 7, 2022, at 10:22 AM, Michele Venturi mailto:dard...@gmail.com>> wrote:

Should I submit a bug report before we even know if it's a
MacPorts specific issue? Or how do we find that out?

Il lun 7 mar 2022, 16:47 Chris Jones mailto:jon...@hep.phy.cam.ac.uk>> ha scritto:



On 07/03/2022 3:31 pm, Michele Venturi wrote:
> I have the required libraries in /usr/lib/swift too,but MPV
is looking
> for them in /opt/local/lib,so it doesn't find them:
>
> otool -l $(which mpv)
> ...
> cmd LC_RPATH
> cmdsize 32
> path /opt/local/lib (offset 12)
>
> Should we change RPATH or add symbolic links?

No, those are not the solutions here. If there is an issue
with the
build on 10.13 we should fix that instead, rather than apply
after-the-fact bandaids.

The first thing to determine is if its a MacPorts specific
issue due to
how the build is performed, or an upstream issue. Either way
please
submit a bug report to macports trac so the discussion on this
can
continue there.

Chris

>
> Michele Venturi
> about.me/dardo82 
>
>
>

>

>
> Michele Venturi
> about.me/dardo82 
>

>

>
>
>
>
> Il giorno lun 7 mar 2022 alle ore 15:46 Ryan Schmidt
> mailto:ryandes...@macports.org>
>> ha scritto:
>
>
>
>     On Mar 7, 2022, at 08:34, Michele Venturi wrote:
>
>      > If I install MPV without Xcode I get an error when I
launch it:
>      >
>      > dyld: Library not loaded:
@rpath/libswiftAVFoundation.dylib
>      >   Referenced from: /opt/local/bin/mpv
>      >   Reason: image not found
>      >
>      > It's missing something,have you tried to execute it
on 10.13?
>
>     I have not.
>
>     I guess you're right, in relation to the Swift language
usage I
>     mentioned earlier, this port does appear to need
>     libswiftAVFoundation.dylib at runtime. And maybe it is
expecting to
>     find it within Xcode on your system. (It depends on what
@rpath
>     expands to. I forget what the command is to interrogate
a binary
>     about its rpaths.)
>
>     Swift is still a new programming language and I don't
think we have
>     many ports in MacPorts that use Swift so I'm not sure if
this should
>     be considered normal or not.
>
>     I see that I have many copies of
libswiftAVFoundation.dylib on my
>     system, within various applications' bundles, so I guess
Apple
>     expects people to include copies of the Swift dylibs
with their
>     application.
>
>     On my 10.15 system, it does not link with
>     @rpath/libswiftAVFoundation.dylib. It links with various
Swift
>     dylibs in /usr/lib/swift. Maybe the port can be made to
do so on
>     10.13 as well.
>
>     You should file a bug report about this mpv problem.
>

Re: MacPorts XCode Installation

[Michele Venturi]

What should I include in the bug report to make it clear?

Il lun 7 mar 2022, 17:25 Marius Schamschula  ha
scritto:

> Michele,
>
> Please submit a MacPorts ticket!
>
> Other users may search trac if they encounter the same issue. We can also
> link to any upstream tickets from there.
>
> On Mar 7, 2022, at 10:22 AM, Michele Venturi  wrote:
>
> Should I submit a bug report before we even know if it's a MacPorts
> specific issue? Or how do we find that out?
>
> Il lun 7 mar 2022, 16:47 Chris Jones  ha
> scritto:
>
>>
>>
>> On 07/03/2022 3:31 pm, Michele Venturi wrote:
>> > I have the required libraries in /usr/lib/swift too,but MPV is looking
>> > for them in /opt/local/lib,so it doesn't find them:
>> >
>> > otool -l $(which mpv)
>> > ...
>> > cmd LC_RPATH
>> > cmdsize 32
>> > path /opt/local/lib (offset 12)
>> >
>> > Should we change RPATH or add symbolic links?
>>
>> No, those are not the solutions here. If there is an issue with the
>> build on 10.13 we should fix that instead, rather than apply
>> after-the-fact bandaids.
>>
>> The first thing to determine is if its a MacPorts specific issue due to
>> how the build is performed, or an upstream issue. Either way please
>> submit a bug report to macports trac so the discussion on this can
>> continue there.
>>
>> Chris
>>
>> >
>> > Michele Venturi
>> > about.me/dardo82 
>> >
>> > <
>> https://about.me/dardo82?promo=email_sig_source=product_medium=email_sig_campaign=gmail_api_content=thumb>
>>
>> >
>> > Michele Venturi
>> > about.me/dardo82
>> > <
>> https://about.me/dardo82?promo=email_sig_source=product_medium=email_sig_campaign=gmail_api_content=thumb>
>>
>> >
>> >
>> >
>> >
>> > Il giorno lun 7 mar 2022 alle ore 15:46 Ryan Schmidt
>> > mailto:ryandes...@macports.org>> ha scritto:
>> >
>> >
>> >
>> > On Mar 7, 2022, at 08:34, Michele Venturi wrote:
>> >
>> >  > If I install MPV without Xcode I get an error when I launch it:
>> >  >
>> >  > dyld: Library not loaded: @rpath/libswiftAVFoundation.dylib
>> >  >   Referenced from: /opt/local/bin/mpv
>> >  >   Reason: image not found
>> >  >
>> >  > It's missing something,have you tried to execute it on 10.13?
>> >
>> > I have not.
>> >
>> > I guess you're right, in relation to the Swift language usage I
>> > mentioned earlier, this port does appear to need
>> > libswiftAVFoundation.dylib at runtime. And maybe it is expecting to
>> > find it within Xcode on your system. (It depends on what @rpath
>> > expands to. I forget what the command is to interrogate a binary
>> > about its rpaths.)
>> >
>> > Swift is still a new programming language and I don't think we have
>> > many ports in MacPorts that use Swift so I'm not sure if this should
>> > be considered normal or not.
>> >
>> > I see that I have many copies of libswiftAVFoundation.dylib on my
>> > system, within various applications' bundles, so I guess Apple
>> > expects people to include copies of the Swift dylibs with their
>> > application.
>> >
>> > On my 10.15 system, it does not link with
>> > @rpath/libswiftAVFoundation.dylib. It links with various Swift
>> > dylibs in /usr/lib/swift. Maybe the port can be made to do so on
>> > 10.13 as well.
>> >
>> > You should file a bug report about this mpv problem.
>> >
>>
>
>

Re: MacPorts XCode Installation

[Marius Schamschula]

Michele,

Please submit a MacPorts ticket!

Other users may search trac if they encounter the same issue. We can also link 
to any upstream tickets from there.

> On Mar 7, 2022, at 10:22 AM, Michele Venturi  wrote:
> 
> Should I submit a bug report before we even know if it's a MacPorts specific 
> issue? Or how do we find that out?
> 
> Il lun 7 mar 2022, 16:47 Chris Jones  > ha scritto:
> 
> 
> On 07/03/2022 3:31 pm, Michele Venturi wrote:
> > I have the required libraries in /usr/lib/swift too,but MPV is looking 
> > for them in /opt/local/lib,so it doesn't find them:
> > 
> > otool -l $(which mpv)
> > ...
> > cmd LC_RPATH
> > cmdsize 32
> > path /opt/local/lib (offset 12)
> > 
> > Should we change RPATH or add symbolic links?
> 
> No, those are not the solutions here. If there is an issue with the 
> build on 10.13 we should fix that instead, rather than apply 
> after-the-fact bandaids.
> 
> The first thing to determine is if its a MacPorts specific issue due to 
> how the build is performed, or an upstream issue. Either way please 
> submit a bug report to macports trac so the discussion on this can 
> continue there.
> 
> Chris
> 
> > 
> > Michele Venturi
> > about.me/dardo82   > >
> > 
> >  >  
> > >
> >  
> >   
> > Michele Venturi
> > about.me/dardo82  
> >  >  
> > >
> >  
> > 
> > 
> > 
> > 
> > Il giorno lun 7 mar 2022 alle ore 15:46 Ryan Schmidt 
> > mailto:ryandes...@macports.org> 
> > >> ha 
> > scritto:
> > 
> > 
> > 
> > On Mar 7, 2022, at 08:34, Michele Venturi wrote:
> > 
> >  > If I install MPV without Xcode I get an error when I launch it:
> >  >
> >  > dyld: Library not loaded: @rpath/libswiftAVFoundation.dylib
> >  >   Referenced from: /opt/local/bin/mpv
> >  >   Reason: image not found
> >  >
> >  > It's missing something,have you tried to execute it on 10.13?
> > 
> > I have not.
> > 
> > I guess you're right, in relation to the Swift language usage I
> > mentioned earlier, this port does appear to need
> > libswiftAVFoundation.dylib at runtime. And maybe it is expecting to
> > find it within Xcode on your system. (It depends on what @rpath
> > expands to. I forget what the command is to interrogate a binary
> > about its rpaths.)
> > 
> > Swift is still a new programming language and I don't think we have
> > many ports in MacPorts that use Swift so I'm not sure if this should
> > be considered normal or not.
> > 
> > I see that I have many copies of libswiftAVFoundation.dylib on my
> > system, within various applications' bundles, so I guess Apple
> > expects people to include copies of the Swift dylibs with their
> > application.
> > 
> > On my 10.15 system, it does not link with
> > @rpath/libswiftAVFoundation.dylib. It links with various Swift
> > dylibs in /usr/lib/swift. Maybe the port can be made to do so on
> > 10.13 as well.
> > 
> > You should file a bug report about this mpv problem.
> > 

Re: MacPorts XCode Installation

[Michele Venturi]

Should I submit a bug report before we even know if it's a MacPorts
specific issue? Or how do we find that out?

Il lun 7 mar 2022, 16:47 Chris Jones  ha scritto:

>
>
> On 07/03/2022 3:31 pm, Michele Venturi wrote:
> > I have the required libraries in /usr/lib/swift too,but MPV is looking
> > for them in /opt/local/lib,so it doesn't find them:
> >
> > otool -l $(which mpv)
> > ...
> > cmd LC_RPATH
> > cmdsize 32
> > path /opt/local/lib (offset 12)
> >
> > Should we change RPATH or add symbolic links?
>
> No, those are not the solutions here. If there is an issue with the
> build on 10.13 we should fix that instead, rather than apply
> after-the-fact bandaids.
>
> The first thing to determine is if its a MacPorts specific issue due to
> how the build is performed, or an upstream issue. Either way please
> submit a bug report to macports trac so the discussion on this can
> continue there.
>
> Chris
>
> >
> > Michele Venturi
> > about.me/dardo82 
> >
> > <
> https://about.me/dardo82?promo=email_sig_source=product_medium=email_sig_campaign=gmail_api_content=thumb>
>
> >
> > Michele Venturi
> > about.me/dardo82
> > <
> https://about.me/dardo82?promo=email_sig_source=product_medium=email_sig_campaign=gmail_api_content=thumb>
>
> >
> >
> >
> >
> > Il giorno lun 7 mar 2022 alle ore 15:46 Ryan Schmidt
> > mailto:ryandes...@macports.org>> ha scritto:
> >
> >
> >
> > On Mar 7, 2022, at 08:34, Michele Venturi wrote:
> >
> >  > If I install MPV without Xcode I get an error when I launch it:
> >  >
> >  > dyld: Library not loaded: @rpath/libswiftAVFoundation.dylib
> >  >   Referenced from: /opt/local/bin/mpv
> >  >   Reason: image not found
> >  >
> >  > It's missing something,have you tried to execute it on 10.13?
> >
> > I have not.
> >
> > I guess you're right, in relation to the Swift language usage I
> > mentioned earlier, this port does appear to need
> > libswiftAVFoundation.dylib at runtime. And maybe it is expecting to
> > find it within Xcode on your system. (It depends on what @rpath
> > expands to. I forget what the command is to interrogate a binary
> > about its rpaths.)
> >
> > Swift is still a new programming language and I don't think we have
> > many ports in MacPorts that use Swift so I'm not sure if this should
> > be considered normal or not.
> >
> > I see that I have many copies of libswiftAVFoundation.dylib on my
> > system, within various applications' bundles, so I guess Apple
> > expects people to include copies of the Swift dylibs with their
> > application.
> >
> > On my 10.15 system, it does not link with
> > @rpath/libswiftAVFoundation.dylib. It links with various Swift
> > dylibs in /usr/lib/swift. Maybe the port can be made to do so on
> > 10.13 as well.
> >
> > You should file a bug report about this mpv problem.
> >
>

Re: MacPorts XCode Installation

[Chris Jones]

On 07/03/2022 3:31 pm, Michele Venturi wrote:
I have the required libraries in /usr/lib/swift too,but MPV is looking 
for them in /opt/local/lib,so it doesn't find them:


otool -l $(which mpv)
...
cmd LC_RPATH
cmdsize 32
path /opt/local/lib (offset 12)

Should we change RPATH or add symbolic links?


No, those are not the solutions here. If there is an issue with the 
build on 10.13 we should fix that instead, rather than apply 
after-the-fact bandaids.


The first thing to determine is if its a MacPorts specific issue due to 
how the build is performed, or an upstream issue. Either way please 
submit a bug report to macports trac so the discussion on this can 
continue there.


Chris



Michele Venturi
about.me/dardo82 

 
	

Michele Venturi
about.me/dardo82 
 





Il giorno lun 7 mar 2022 alle ore 15:46 Ryan Schmidt 
mailto:ryandes...@macports.org>> ha scritto:




On Mar 7, 2022, at 08:34, Michele Venturi wrote:

 > If I install MPV without Xcode I get an error when I launch it:
 >
 > dyld: Library not loaded: @rpath/libswiftAVFoundation.dylib
 >   Referenced from: /opt/local/bin/mpv
 >   Reason: image not found
 >
 > It's missing something,have you tried to execute it on 10.13?

I have not.

I guess you're right, in relation to the Swift language usage I
mentioned earlier, this port does appear to need
libswiftAVFoundation.dylib at runtime. And maybe it is expecting to
find it within Xcode on your system. (It depends on what @rpath
expands to. I forget what the command is to interrogate a binary
about its rpaths.)

Swift is still a new programming language and I don't think we have
many ports in MacPorts that use Swift so I'm not sure if this should
be considered normal or not.

I see that I have many copies of libswiftAVFoundation.dylib on my
system, within various applications' bundles, so I guess Apple
expects people to include copies of the Swift dylibs with their
application.

On my 10.15 system, it does not link with
@rpath/libswiftAVFoundation.dylib. It links with various Swift
dylibs in /usr/lib/swift. Maybe the port can be made to do so on
10.13 as well.

You should file a bug report about this mpv problem.

Re: MacPorts XCode Installation

[Michele Venturi]

I have the required libraries in /usr/lib/swift too,but MPV is looking for
them in /opt/local/lib,so it doesn't find them:

otool -l $(which mpv)
...
cmd LC_RPATH
cmdsize 32
path /opt/local/lib (offset 12)

Should we change RPATH or add symbolic links?

Michele Venturi
about.me/dardo82


Michele Venturi
about.me/dardo82



Il giorno lun 7 mar 2022 alle ore 15:46 Ryan Schmidt <
ryandes...@macports.org> ha scritto:

>
>
> On Mar 7, 2022, at 08:34, Michele Venturi wrote:
>
> > If I install MPV without Xcode I get an error when I launch it:
> >
> > dyld: Library not loaded: @rpath/libswiftAVFoundation.dylib
> >   Referenced from: /opt/local/bin/mpv
> >   Reason: image not found
> >
> > It's missing something,have you tried to execute it on 10.13?
>
> I have not.
>
> I guess you're right, in relation to the Swift language usage I mentioned
> earlier, this port does appear to need libswiftAVFoundation.dylib at
> runtime. And maybe it is expecting to find it within Xcode on your system.
> (It depends on what @rpath expands to. I forget what the command is to
> interrogate a binary about its rpaths.)
>
> Swift is still a new programming language and I don't think we have many
> ports in MacPorts that use Swift so I'm not sure if this should be
> considered normal or not.
>
> I see that I have many copies of libswiftAVFoundation.dylib on my system,
> within various applications' bundles, so I guess Apple expects people to
> include copies of the Swift dylibs with their application.
>
> On my 10.15 system, it does not link with
> @rpath/libswiftAVFoundation.dylib. It links with various Swift dylibs in
> /usr/lib/swift. Maybe the port can be made to do so on 10.13 as well.
>
> You should file a bug report about this mpv problem.
>
>

Re: MacPorts XCode Installation

[Ryan Schmidt]

On Mar 7, 2022, at 08:34, Michele Venturi wrote:

> If I install MPV without Xcode I get an error when I launch it:
> 
> dyld: Library not loaded: @rpath/libswiftAVFoundation.dylib
>   Referenced from: /opt/local/bin/mpv
>   Reason: image not found
> 
> It's missing something,have you tried to execute it on 10.13?

I have not.

I guess you're right, in relation to the Swift language usage I mentioned 
earlier, this port does appear to need libswiftAVFoundation.dylib at runtime. 
And maybe it is expecting to find it within Xcode on your system. (It depends 
on what @rpath expands to. I forget what the command is to interrogate a binary 
about its rpaths.)

Swift is still a new programming language and I don't think we have many ports 
in MacPorts that use Swift so I'm not sure if this should be considered normal 
or not.

I see that I have many copies of libswiftAVFoundation.dylib on my system, 
within various applications' bundles, so I guess Apple expects people to 
include copies of the Swift dylibs with their application.

On my 10.15 system, it does not link with @rpath/libswiftAVFoundation.dylib. It 
links with various Swift dylibs in /usr/lib/swift. Maybe the port can be made 
to do so on 10.13 as well.

You should file a bug report about this mpv problem.

Re: MacPorts XCode Installation

[Michele Venturi]

If I install MPV without Xcode I get an error when I launch it:


dyld: Library not loaded: @rpath/libswiftAVFoundation.dylib

  Referenced from: /opt/local/bin/mpv

  Reason: image not found


It's missing something,have you tried to execute it on 10.13?

Michele Venturi
about.me/dardo82



Il giorno lun 7 mar 2022 alle ore 15:10 Ryan Schmidt <
ryandes...@macports.org> ha scritto:

> On Mar 7, 2022, at 08:06, Michele Venturi wrote:
>
> > There is no binary of MPV for OSX 10.13.6? It's too old?
>
> I see a binary of mpv for macOS 10.13:
>
> http://packages.macports.org/mpv/
>
> We produce binaries for Mac OS X 10.6 and later.
>
> Only binaries of default variants are produced. If you are changing the
> variant selection, then you will have to build from source.
>
> There are other reasons why you might not be able to use our binaries. For
> example, if you have built MacPorts base from source in a prefix other than
> /opt/local then you cannot use our binaries.
>
>

Re: MacPorts XCode Installation

[Ryan Schmidt]

On Mar 7, 2022, at 08:06, Michele Venturi wrote:

> There is no binary of MPV for OSX 10.13.6? It's too old? 

I see a binary of mpv for macOS 10.13:

http://packages.macports.org/mpv/

We produce binaries for Mac OS X 10.6 and later.

Only binaries of default variants are produced. If you are changing the variant 
selection, then you will have to build from source.

There are other reasons why you might not be able to use our binaries. For 
example, if you have built MacPorts base from source in a prefix other than 
/opt/local then you cannot use our binaries.

Re: MacPorts XCode Installation

[Michele Venturi]

There is no binary of MPV for OSX 10.13.6? It's too old?

Il lun 7 mar 2022, 13:41 Ryan Schmidt  ha scritto:

> On Mar 7, 2022, at 06:14, Michele Venturi wrote:
>
> > Web browsers are even more complicated but
> > you do not need to install xcode to use safari...
>
> But you do need to install Xcode to *compile* Safari.
>
> In the same way, you need to install Xcode to *compile* mpv, but you do
> not need Xcode to receive a binary of mpv from our servers, nor do you need
> Xcode to run an mpv (or any other port) that you've already installed with
> MacPorts.
>
>

Re: Running a mail server via MacPorts on macOS Monterey

[Ben Greenfield via macports-users]

Thanks for this outline. This has been on my todo list for a couple of years

I imagine you are using the host system’s Open Directory directory for 
authentication.

Thanks,

Ben



> On Mar 4, 2022, at 7:12 PM, Steve Wardle via macports-users 
>  wrote:
> 
> I initially replied to Gerben off list but I am running my mail server on 
> macOS 12.2.1.
> 
> Using macports packages for:
>   postfix +dovecot_sasl +ldap +pcre +smtputf8 +tls
>   amavisd-new
>   clamav
>   dovecot
>   libmilter
>   unbound +libevent
>   certbot
> 
> Installing / building from source:
>   opendkim
>   opendmarc
>   policyd-spf
>   postfwd
>   postwhite
>   sshguard
> 
> Steve
> 
>> On 3 Mar 2022, at 13:38, Gerben Wierda via macports-users 
>> > > wrote:
>> 
>> Apart from Steven Smith, are there other users here that run a mail server 
>> setup via MacPorts? And is already someone else running on Monterey?
>> 
>> I am and I’d like to link up to compare the situations, issues, etc. 
>> 
>> Gerben Wierda (LinkedIn )
>> R IT Strategy  (main site)
>> Book: Chess and the Art of Enterprise Architecture 
>> 
>> Book: Mastering ArchiMate 
>> 
> 

Re: Running a mail server via MacPorts on macOS Monterey

[Steven Smith]

As a counterpoint, macOS is configurable with all the BSD flags you need to 
configure a performant server. Just add these options to /etc/sysctl.conf, 
which although does not exist in macOS 12, can easily be edited and works 
across reboots.

I just did this myself for a native VPN server using net.inet.ip.forwarding, 
net.inet6.ip6.forwarding, and kern.ipc.somaxconn.

The mail server tools used in the old macOS Server.app really have been 
(greatly) surpassed by current alternatives, e.g. rspamd instead of 
spamassassin, and Apache Solar searches versus whatever the old slow dovecot 
search plugin was. I used to run a mail server on Server.app, and the mail 
server configure in the port mail-server is MUCH more performant and nicer.

Furthermore, macOS has migrated to much better kernel-level security tools like 
pfctl that more than offset the pain of migration to a macOS-specific 
environment.

All-in-all, the mail and other servers I’ve observed running on macOS have all 
been rock solid, at the expense of the necessity of adapting from cookie-cutter 
Linux or BSD options, but with the simplified workflow of not needing to 
maintain another VPS somewhere.


> On Mar 5, 2022, at 8:56 AM, Ralph Seichter via macports-users 
>  wrote:
> 
> While MacPorts provides the necessary ports for running a mail server on
> macOS, I'd suggest an alternative approach if you are dead set on using
> a Mac as the server machine. As mentioned here before, Apple is not
> making it easy to use regular macOS for server use, and this seems to be
> a deliberate decision on their end.



smime.p7s
Description: S/MIME cryptographic signature

Re: MacPorts XCode Installation

[Ryan Schmidt]

On Mar 7, 2022, at 06:14, Michele Venturi wrote:

> Web browsers are even more complicated but
> you do not need to install xcode to use safari...

But you do need to install Xcode to *compile* Safari.

In the same way, you need to install Xcode to *compile* mpv, but you do not 
need Xcode to receive a binary of mpv from our servers, nor do you need Xcode 
to run an mpv (or any other port) that you've already installed with MacPorts.

Re: MacPorts XCode Installation

[Michele Venturi]

Web browsers are even more complicated but
you do not need to install xcode to use safari...

Il lun 7 mar 2022, 13:07 Ryan Schmidt  ha scritto:

> On Mar 7, 2022, at 06:02, Michele Venturi wrote:
>
> > Sadly xcode is needed even for something as simple as
> > a media player, for example mpv, I wonder why actually.
>
> Media players are probably extremely complicated pieces of software.
> Hardly what I would call simple.
>
> In the case of mpv, it requires Xcode, on recent OS versions, because
> parts of it are built using the Swift language, and this was thought to be
> the only way to get those parts to build properly. See
> https://github.com/macports/macports-ports/commit/8222cfaa4124483d2faad4f35a209885d440dd61
> .
>
> mpv is a difficult piece of software to get to build properly. I recently
> committed numerous changes to hopefully fix many of those problems in the
> mpv port, but there are probably still other problems remaining.

Re: MacPorts XCode Installation

[Ryan Schmidt]

On Mar 7, 2022, at 06:02, Michele Venturi wrote:

> Sadly xcode is needed even for something as simple as
> a media player, for example mpv, I wonder why actually.

Media players are probably extremely complicated pieces of software. Hardly 
what I would call simple.

In the case of mpv, it requires Xcode, on recent OS versions, because parts of 
it are built using the Swift language, and this was thought to be the only way 
to get those parts to build properly. See 
https://github.com/macports/macports-ports/commit/8222cfaa4124483d2faad4f35a209885d440dd61.

mpv is a difficult piece of software to get to build properly. I recently 
committed numerous changes to hopefully fix many of those problems in the mpv 
port, but there are probably still other problems remaining.

Re: MacPorts XCode Installation

[Michele Venturi]

Sadly xcode is needed even for something as simple as
a media player, for example mpv, I wonder why actually.


Il lun 7 mar 2022, 12:38 Ryan Schmidt  ha scritto:

>
>
> On Feb 26, 2022, at 12:04, Haren Samarasinghe wrote:
>
> > After reading the installation guide [1], quite a few people that I've
> introduced MacPorts to have thought that a full XCode installation is
> required. They're uncertain of doing this due to the large amount of space
> it requires.
> >
> > In reality, I'd say that the majority of ports only require the command
> line tools. In the scenarios where XCode is required for a port, the user
> is normally alerted to this.
> >
> > I was planning on changing the docs [1][2] to show that XCode isn't
> required, but I wanted to first check whether this would be an acceptable
> change.
>
> Yes that's a good idea.
>
> If the port you're installing (and its dependencies) are available as
> binaries, you do not need Xcode and you do not need the command line tools.
> MacPorts will just install the binaries. MacPorts will probably print
> warnings about Xcode and/or CLT being missing but in this case they can be
> ignored.
>
> If the port (or its dependencies) are not available as binaries, you'll
> probably need either Xcode or the command line tools. If you don't have
> them installed, you'll get warnings, and then probably a build failure.
>
> Some ports need Xcode to build. These are (hopefully) marked with
> "use_xcode yes". If you try to install such a port and you do not have
> Xcode installed, MacPorts will tell you to install it.
>
>

Re: MacPorts XCode Installation

[Ryan Schmidt]

On Feb 26, 2022, at 12:04, Haren Samarasinghe wrote:

> After reading the installation guide [1], quite a few people that I've 
> introduced MacPorts to have thought that a full XCode installation is 
> required. They're uncertain of doing this due to the large amount of space it 
> requires.
> 
> In reality, I'd say that the majority of ports only require the command line 
> tools. In the scenarios where XCode is required for a port, the user is 
> normally alerted to this.
> 
> I was planning on changing the docs [1][2] to show that XCode isn't required, 
> but I wanted to first check whether this would be an acceptable change.

Yes that's a good idea.

If the port you're installing (and its dependencies) are available as binaries, 
you do not need Xcode and you do not need the command line tools. MacPorts will 
just install the binaries. MacPorts will probably print warnings about Xcode 
and/or CLT being missing but in this case they can be ignored.

If the port (or its dependencies) are not available as binaries, you'll 
probably need either Xcode or the command line tools. If you don't have them 
installed, you'll get warnings, and then probably a build failure.

Some ports need Xcode to build. These are (hopefully) marked with "use_xcode 
yes". If you try to install such a port and you do not have Xcode installed, 
MacPorts will tell you to install it.

Re: IRC channel

[g5pw]

We could try a complete reinstall, maybe that fixes the problem? Unfortunately 
I'm not really versed in Meteor.js or modern JS :/

> On 7 Mar 2022, at 10:25, Mojca Miklavec  wrote:
> 
> 
> Aljaž is aware of the problem.
> 
> He was hoping that the latest upgrade would fix the issue, but
> apparently it doesn't:
>https://github.com/RocketChat/Rocket.Chat/issues/24460 
> 
>https://github.com/RocketChat/Rocket.Chat/issues/24355 
> 
> 
> I'm not sure what could/should be done (other than someone stepping up
> to help the rocketchat team fix the issue, or migrate to something
> else; we discarded the idea of using Discord as it's being blocked in
> some countries).

Re: IRC channel

[Mojca Miklavec]

On Mon, 7 Mar 2022 at 04:06, Michele Venturi wrote:
>
> Anyway RocketChat should be fixed as it doesn't work...

Aljaž is aware of the problem.

He was hoping that the latest upgrade would fix the issue, but
apparently it doesn't:
https://github.com/RocketChat/Rocket.Chat/issues/24460
https://github.com/RocketChat/Rocket.Chat/issues/24355

I'm not sure what could/should be done (other than someone stepping up
to help the rocketchat team fix the issue, or migrate to something
else; we discarded the idea of using Discord as it's being blocked in
some countries).

Mojca