<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><br class=""><div class=""><br class=""></div><div class=""><div><blockquote type="cite" class=""><div class="">Am 28.03.2025 um 12:24 schrieb Ryan Carsten Schmidt <<a href="mailto:ryandesign@macports.org" class="">ryandesign@macports.org</a>>:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="content-type" content="text/html; charset=utf-8" class=""><div dir="auto" class=""><div dir="ltr" class=""></div><div dir="ltr" class="">On Mar 28, 2025, at 04:32, Christoph Kukulies wrote:</div><div dir="ltr" class=""><blockquote type="cite" class=""><br class=""></blockquote></div><blockquote type="cite" class=""><div dir="ltr" class=""><span class="">% port livecheck opencascade</span><br class=""><span class="">opencascade seems to have been updated (port version: 7.8.0, new version:</span><br class=""><span class="">7.9.0</span><br class=""><span class=""></span><br class=""><span class="">How do I activate 7.9.0 ?</span></div></blockquote><br class=""><div class="">The high-level overview is that one would change the Portfile and the files directory in whatever way is necessary to allow the new version to install. That's intentionally vague because the specifics vary from port to port and often even from one version of a port to another. Figuring out what is needed to update a port to a new version is the bulk of the work done by MacPorts contributors.</div><div class=""><br class=""></div><div class="">Ideally the port's maintainer timely notices when new updates are available and updates it. If they don't or for ports with no maintainer, anyone can submit an update as a pull request (ideally) or by attaching a diff to a ticket. </div><div class=""><br class=""></div><div class="">In the simplest case, the version field would be updated to the new version and the checksums field would be updated to match. These most basic steps are explained in detail here:</div><div class=""><br class=""></div><div class=""><a href="https://trac.macports.org/wiki/howto/Upgrade" class="">https://trac.macports.org/wiki/howto/Upgrade</a></div><div class=""><br class=""></div><div class="">If the port has tests enabled, ideally one would run them and see if any new test failures appear as a result of the update. </div><div class=""><br class=""></div><div class="">Often, more than that will be needed. For example, an existing patch file may need to be updated so that it continues to work with the new version. Or the patch may no longer be needed because it was already incorporated into the new version. Or a new patch may be needed to fix a new bug that wasn't present in the old version. The new version may have new dependencies or it may no longer need existing dependencies. Etc, etc. </div><div class=""><br class=""></div></div></div></blockquote></div><br class=""></div></div></body></html>