<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="">I have a new game port done, Endless Sky <<a href="https://endless-sky.github.io" class="">https://endless-sky.github.io</a>>.</div><div class=""><br class=""></div><div class="">It requires "libjpeg-turbo" rather than “jpeg" and so I came across the mess with the conflict with jpeg: </div><div class=""><br class=""></div><div class=""><<a href="https://trac.macports.org/ticket/38907" class="">https://trac.macports.org/ticket/38907</a>></div><div class=""><br class=""></div><div class="">and </div><div class=""><br class=""></div><div class=""><<a href="https://libjpeg-turbo.org/About/Jpeg-9" class="">https://libjpeg-turbo.org/About/Jpeg-9</a>></div><div class=""><br class=""></div><div class="">Homebrew installs them in parallel, which I guess is all we can realistically do given the API9 vs API8 business.</div><div class=""><br class=""></div><div class="">We could do that easily enough. It doesn’t look like libjpeg-turbo can be a drop in replacement for jpeg any more as they now have different APIs. </div><div class=""><br class=""></div><div class="">Anyone have any ideas on [ how to / if we should ] try to resolve this?</div><div class=""><br class=""></div><div class="">Ken</div></body></html>