Re: Migration doc suggestion - chsh

[Ryan Schmidt]

On Nov 27, 2020, at 15:50, Kevin Horton wrote:

> I'm apparently a slow learner, but once again I forgot to change my login 
> shell back to one supplied by Apple before migrating to Big Sur (I had been 
> using.
> 
> Suggestion - add a step to the Migration docs, before the step that removes 
> all ports.  If the user is using a default shell provided by Macports, do a 
> 'chsh -s /bin/bash' (or other Apple supplied shell) before removing all ports.

The wiki can be edited by anyone.

Re: Port Application Issues (Launching Issues)

[Ryan Schmidt]

On Nov 27, 2020, at 18:25, Riccardo Mottola wrote:

> However, only native Cocoa apps wil install an .app bundle inside the 
> MacPorts folder. E.g. emacs, gimp do that if they are compiled in the 
> "+quartz" variant. Other apps if not Mac native will have their own launch 
> method which will not be as straight-forward.

There are some ports that install app bundles in the /Applications/MacPorts 
folder even though they are not native Cocoa apps. These app bundles are 
intended as a convenience that can be used to launch applications from the 
Finder, Dock, LaunchPad, Spotlight, etc., but other than that they don't behave 
like normal Mac apps. For example, dragging a document icon to it won't open it 
into the application, the application icon may continue bouncing in the Dock 
after the app is launched, clicking the icon in the Dock after the app is 
launched won't switch to the app, etc.

Usually though, software that is not a native Mac Cocoa app will not have an 
app bundle in /Applications/MacPorts and you'll usually run it from the 
terminal. The "port contents" command tells you what was installed and where so 
that you know what to run.

Re: MacPorts on Apple Silicon Macs (was: Re: info)

[Ryan Schmidt]

On Nov 27, 2020, at 09:15, Giovanni Cantele wrote:

> is there any ongoing project for porting the whole macports staff on the new 
> Apple silicon architecture?
> What happens to those who extensively make use of macports and have bought 
> the recent released MacBook Pro running on the new processors?

Right now we have probably thousands ports that are broken due to three 
different issues, and Apple Silicon machines are affected by all three issues:

1. Xcode 12 makes implicit declaration of functions an error instead of a 
warning. Apple made this change in order to prevent problems that would 
otherwise occur on Apple Silicon machines but it will take a long time before 
either we or the developers of the software patch all of our ports to 
accommodate this change. Instructions for developers wishing to help fix these 
problems are here: 
https://lists.macports.org/pipermail/macports-dev/2020-November/042647.html and 
in my follow-up to that message.

2. macOS Big Sur is version 11, and a lot of software did not anticipate that 
such a version number of macOS would ever exist and fail to build as a result. 
All software that uses autotools and libtool and relies on the use of symbols 
that are undefined at build time is affected, for example, but there are 
limitless other ways that developers could have and did write their software so 
that it would only work on macOS 10.x. The libtool issue may have a simple fix 
that we could use: https://trac.macports.org/ticket/61584 but we have not 
employed that yet.

3. Many ports fail to build on Apple Silicon machines for a variety of other 
reasons which we will need to investigate and fix as we encounter them one by 
one.

MacPorts volunteers are working with the developers of the affected software to 
fix it and fix our ports as time permits. You or anyone interested can help by 
reporting bugs, either to us in the case of ancient software or to the 
developers of the software if it is still being developed, or by fixing the 
problem and sending us or the developers the fix. We have tens of thousands of 
ports in MacPorts and it's not always clear to us which ones people use. By 
filing a bug report about a port or Cc'ing yourself on an existing report about 
a problem, you can help us identify which problems we need to focus on fixing.

I previously advised that if you want to avoid issues with MacPorts ports while 
we try to work this all out, don't upgrade to Big Sur yet. See 
https://lists.macports.org/pipermail/macports-users/2020-November/048940.html. 
I would also advise not upgrading to Xcode 12 yet on Catalina. Since Apple 
Silicon Macs require Big Sur and Xcode 12.2, my recommendation extends to not 
buying an Apple Silicon Mac yet, despite how fantastic I'm sure they will be.

Re: Port Application Issues (Launching Issues)

[Uli Wienands]

In general, you can launch an app from the terminal using open (e.g. 
open /Applications/TextEdit.app).


Application bundles often have the actual app somewhere inside the 
Contents/MacOS folder that you can open in terminal by just executing it 
(e.g. /Applications/TextEdit.app//Contents/MacOS/TextEdit). Occasionally 
I have also seem an alias inside the app's Contents folder to do this.


On my system, MacPorts puts its GUI applications into a MacPorts folder 
in /Applications. The rest, including those that use X11, goes into 
/opt/local/bin.


Uli


On 11/27/20 6:25 PM, Riccardo Mottola via macports-users wrote:

Hi,

Jonathan Allen via macports-users wrote:
The problem is, I can’t find the application icon at all and even 
searched the MacPorts help pages to see if there was a “launch this 
application” command and didn’t see one. I am a first time MacPorts 
user. How do I fix this so I can launch the HomeBank application, or 
have it show up in the MacPorts folder of the applications folder.



I don't use HomeBank, so I don't know the details. However, only 
native Cocoa apps wil install an .app bundle inside the MacPorts 
folder. E.g. emacs, gimp do that if they are compiled in the "+quartz" 
variant. Other apps if not Mac native will have their own launch 
method which will not be as straight-forward.


Riccardo

Re: Port Application Issues (Launching Issues)

[Riccardo Mottola via macports-users]

Hi,

Jonathan Allen via macports-users wrote:

The problem is, I can’t find the application icon at all and even searched the 
MacPorts help pages to see if there was a “launch this application” command and 
didn’t see one. I am a first time MacPorts user. How do I fix this so I can 
launch the HomeBank application, or have it show up in the MacPorts folder of 
the applications folder.



I don't use HomeBank, so I don't know the details. However, only native 
Cocoa apps wil install an .app bundle inside the MacPorts folder. E.g. 
emacs, gimp do that if they are compiled in the "+quartz" variant. Other 
apps if not Mac native will have their own launch method which will not 
be as straight-forward.


Riccardo

Re: MacPorts 2.6.4 has been released

[Riccardo Mottola via macports-users]

  
  
Hi!
  
  Joshua Root wrote:


  The MacPorts Project is pleased to announce the release of version
2.6.4. This is a bugfix release with small changes only. See the
ChangeLog [1] for the list of changes.


thank you Joshua! Just updated on 10.7 and 10.5 32bit... seems fine!
now the hard part is to upgrade the packages :)

Releases are always a chore, I know that - I have software that has
to be released since months!

if that works fine, I have 10.6 and especially 10.5 PPC to do!


Riccardo
  

Migration doc suggestion - chsh

[Kevin Horton]

I'm apparently a slow learner, but once again I forgot to change my login shell 
back to one supplied by Apple before migrating to Big Sur (I had been using.

Suggestion - add a step to the Migration docs, before the step that removes all 
ports.  If the user is using a default shell provided by Macports, do a 'chsh 
-s /bin/bash' (or other Apple supplied shell) before removing all ports.

Thanks for MacPorts.

Kevin

Re: info

[Artem Loenko via macports-users]

Hello,

I am in the same boat (and have switched from HomeBrew to MacPorts a few weeks 
ago, so, maybe I am wrong). 

MacPorts as a tool works just fine on Macs with Apple Silicon, but many ports 
are “broken” and have to be fixed. Most of them just do not compile for 
`arm64`, and it is not MacPorts fault, some - do not compile due to MacPorts 
configuration (rare cases). So far, as far as I understand, the best course of 
action is to report all broken ports to the MacPorts tracker and to developers 
of the tool that does not compile for `arm64` arch. For example, this is a 
ticket about broken Neovim (https://trac.macports.org/ticket/61550 
), but it does not compile due to 
issues on the NeoVim side (that’s why I started a discussion with them 
(https://github.com/neovim/neovim/issues/13399 
).

I use the following `make` target to install MacPorts on Apple Silicon or you 
can just download the package from the site 
(https://www.macports.org/install.php ):

```
macports: ## Install/Upgrade MacPorts
ifeq (, $(shell which port))
$(eval TEMP_PKG := $(shell mktemp -t macports).pkg)
curl --silent --output $(TEMP_PKG) --remote-name 
https://distfiles.macports.org/MacPorts/MacPorts-2.6.4_1-11-BigSur.pkg 
sudo installer -pkg $(TEMP_PKG) -target /
rm -Rf $(TEMP_PKG)
endif
sudo port selfupdate
```

Most of the tools I use just work:

```
The following ports are currently installed:
  autoconf @2.69_5 (active)
  automake @1.16.3_0 (active)
  carthage @0.35.0_0 (active)
  fish @3.1.2_0 (active)
  fzf @0.24.3_0 (active)
  gettext @0.19.8.1_2 (active)
  icu @67.1_2 (active)
  ninja @1.10.1_0 (active)
  tig @2.5.1_0+doc (active)
  tmux @3.1c_0 (active)
``

Regards,
Artem

> On 27 Nov 2020, at 15:37, Jeffrey Walton  wrote:
> 
> On Fri, Nov 27, 2020 at 10:27 AM Giovanni Cantele
>  wrote:
>> 
>> Dear All,.
>> 
>> I’m searching the web but I cannot find any response to the following 
>> question:
>> 
>> is there any ongoing project for porting the whole macports staff on the new 
>> Apple silicon architecture?
>> What happens to those who extensively make use of macports and have bought 
>> the recent released MacBook Pro running on the new processors?
> 
> There are several recent threads about support of the latest hardware
> and software at:
> 
>  * 
> https://lists.macports.org/pipermail/macports-users/2020-November/thread.html
> 
> I understand Macports is working through the issues as they encounter
> them during testing before a release.
> 
> I'm guessing it is a bigger task than just supporting a new OS release.
> 
> Jeff

Re: info

[Jeffrey Walton]

On Fri, Nov 27, 2020 at 10:27 AM Giovanni Cantele
 wrote:
>
> Dear All,.
>
> I’m searching the web but I cannot find any response to the following 
> question:
>
> is there any ongoing project for porting the whole macports staff on the new 
> Apple silicon architecture?
> What happens to those who extensively make use of macports and have bought 
> the recent released MacBook Pro running on the new processors?

There are several recent threads about support of the latest hardware
and software at:

  * 
https://lists.macports.org/pipermail/macports-users/2020-November/thread.html

I understand Macports is working through the issues as they encounter
them during testing before a release.

I'm guessing it is a bigger task than just supporting a new OS release.

Jeff

info

[Giovanni Cantele]

Dear All,.

I’m searching the web but I cannot find any response to the following question:

is there any ongoing project for porting the whole macports staff on the new 
Apple silicon architecture?
What happens to those who extensively make use of macports and have bought the 
recent released MacBook Pro running on the new processors?

Thanks you in advance.

Giovanni