<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
<style>
div.plaintext { white-space: normal; }
body { font-family: sans-serif; }
blockquote.embedded,div.plaintext blockquote { margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #777777; color: #777777; }
blockquote.embedded blockquote.embedded,div.plaintext blockquote blockquote { border-left-color: #999999; color: #999999; }
blockquote.embedded blockquote.embedded blockquote.embedded,div.plaintext blockquote blockquote blockquote { border-left-color: #BBBBBB; color: #BBBBBB; }
blockquote.embedded,div.plaintext blockquote a { color: #777777; }
blockquote.embedded blockquote.embedded,div.plaintext blockquote blockquote a { color: #999999; }
blockquote.embedded blockquote.embedded blockquote.embedded,div.plaintext blockquote blockquote blockquote a { color: #BBBBBB; }
div.plaintext math[display="inline"] > mrow { padding:5px; }
div.plaintext div.footnotes li p { margin: 0.2em 0; }
div.plaintext .task-list-item { list-style-type: none; }
</style>
</head>
<body><div class="plaintext"><p dir="auto">On 2024-08-20 at 15:32:44 UTC-0400 (Tue, 20 Aug 2024 15:32:44 -0400)
<br />
Nate Ijams via macports-users <nate@ijams.me>
<br />
is rumored to have said:</p>
<blockquote><p dir="auto">And I suppose one follow up, if that is the case: how are upgrades handled by MacPorts when someone has originally installed a package from source vs binary?</p>
<p dir="auto">Take this scenario:
<br />
– Install package X from source;
<br />
– Install package Y from binary;
<br />
– Later, both packages are upgraded in the ports tree; and
<br />
– I run `port upgrade outdated`.</p>
<p dir="auto">Will X be upgraded from source, and Y from binary, so long as I do not run the command with `-s` or `b`? Or is the history ignored, and both will be upgraded by default from binary? Or is there a different behavior?</p>
</blockquote><p dir="auto">There is no coherent history of actions maintained by MacPorts. The install/upgrade logs get cleaned up by default when everything goes right. It's more like the FreeBSD Ports system than it is like the major Linux package managers.</p>
<p dir="auto">By default 'port upgrade' tries to use pre-built binaries. Note that there are never pre-built binaries available for non-standard variants, so if you've built from source with a variant, it will always be upgraded from source.</p>
</div><div id="391C2EDB-51F2-44BE-8BBE-77E1377A3737"><pre>
bill@scconsult.com or billcole@apache.org
(AKA @grumpybozo@toad.social and many *@billmail.scconsult.com addresses)
Not Currently Available For Hire
</pre></div>
</body>
</html>