<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#333333">
<div class="moz-cite-prefix">
<pre>On 11/12/17 17:58 , Ryan Schmidt wrote:</pre>
</div>
<blockquote
cite="mid:E9FFC957-5FF5-400C-8A90-F9784592C1C4@macports.org"
type="cite">Hi Eric. You should write to the macports-users
mailing list for help using MacPorts.</blockquote>
<pre>√ Done - I'm here. :)</pre>
<pre>
</pre>
<blockquote
cite="mid:E9FFC957-5FF5-400C-8A90-F9784592C1C4@macports.org"
type="cite">
<pre wrap="">Lion is old. If possible on your Mac, please consider upgrading to a newer version of macOS.
</pre>
</blockquote>
<pre>Yes, I'll maybe go to ML. I stopped at Lion and didn't think ML brought much more to it, but it seems to be the bottom low version today. On my way to migrate my Mac Pro -> mini and the run it off-line. Perhaps I should do a clean install of ML then.</pre>
<pre>
</pre>
<blockquote
cite="mid:E9FFC957-5FF5-400C-8A90-F9784592C1C4@macports.org"
type="cite">
<pre wrap="">Yes, you can construct lists of ports by exclusion on the command line, for example:
sudo port upgrade outdated and not go
// ... //
sudo port upgrade outdated and not \( go mongo-tools \)
</pre>
</blockquote>
<pre>Thanks! That'll be fine. I'll use an alias|function to make it easy to go.</pre>
<pre>
</pre>
<blockquote
cite="mid:E9FFC957-5FF5-400C-8A90-F9784592C1C4@macports.org"
type="cite">
<pre wrap="">No, there is no configuration file in which you could specify a list of ports to exclude. I don't think we really want to go down the path of making that easier, because MacPorts was designed with the expectation that you will upgrade all of your ports, and selectively excluding ports can lead to problems.</pre>
</blockquote>
<pre>Yes, I understand that. It just felt like a common way to do it. And since there's a simular way to add things (ie. variants.conf) I guess that was the way to go.</pre>
<pre>// Perhaps I should uninstall it and install it manually instead - just to get it out of the MP system.
- - -
</pre>
<blockquote
cite="mid:E9FFC957-5FF5-400C-8A90-F9784592C1C4@macports.org"
type="cite">
<pre><tt>Looks like Dan, the maintainer of the failing port, osxfuse, hasn't responded to the ticket. It's fine to send a message to the macports-dev mailing list asking if another developer could look into it.</tt></pre>
</blockquote>
<pre>Ok, thanks. I'll do that.
- - -
</pre>
<blockquote
cite="mid:E9FFC957-5FF5-400C-8A90-F9784592C1C4@macports.org"
type="cite">
<pre wrap="">This didn't used to be a problem, because we would copy the distfiles to our own server which uses a configuration that old OS versions can still talk to. But we are not automatically mirroring new distfiles at this time. I would like to get this back online soon, which will solve this problem. The issue is tracked here:
<a class="moz-txt-link-freetext" href="https://trac.macports.org/ticket/53347">https://trac.macports.org/ticket/53347</a>
I have manually mirrored the distfiles for the specific Python ports you mentioned, so you should now be able to install them on Mountain Lion or earlier.
</pre>
</blockquote>
<pre>Thank you so much - that was really helpful.</pre>
<pre>
· Eric
</pre>
</body>
</html>