<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><div><blockquote type="cite" class=""><div class="">Am 12.01.2021 um 02:46 schrieb Ryan Schmidt <<a href="mailto:ryandesign@macports.org" class="">ryandesign@macports.org</a>>:</div><br class="Apple-interchange-newline"><div class=""><div class="">On Jan 11, 2021, at 09:41, Janosch Peters wrote:<br class=""><br class=""><blockquote type="cite" class="">I am struggling to create working port file for sparkle(<a href="https://github.com/sparkle-project/Sparkle" class="">https://github.com/sparkle-project/Sparkle</a>). All targets contained in the Xcode project are building with no errors but when I build & install sparkle via macports and start the „Sparkle Test App“ app bundle I get this: <br class=""><br class="">2021-01-11 16:22:56.277 Sparkle Test App[66399:870691] Unable to load nib file: MainMenu, exiting<br class=""></blockquote><br class="">It might help if you attach or provide a link to your WIP portfile so that we can try it out.<br class=""><br class="">Also, how do you envision a sparkle port being useful in MacPorts? Being an automatic update framework, the way someone would usually use sparkle is by incorporating it into their own project's source code. That's how we normally encounter sparkle in MacPorts, and then we have to expend some effort in figuring out how to remove sparkle from that project, since we don't want that functionality in ports installed by MacPorts. (MacPorts, not the project itself via sparkle, is responsible for updating things.)<br class=""><br class=""></div></div></blockquote></div><div class=""><br class=""></div><div class=""><div class="">Hi Ryan,</div><div class=""><br class=""></div><div class="">I need sparkle as a dependency for the new <a href="https://github.com/macports/macports-ports/pull/9590" class="">MacPass</a> port. Your points about sparkle are of course valid. When I wrote the message I thought it might still be nice to give users the choice to use it or not - via a variant for instance. Also, I thought it might be easier to satisfy the dependency for MacPass rather than to remove it via patches.</div><div class=""><br class=""></div><div class="">But it turned out that removing sparkle from MacPass is pretty easy and also I ran into other problems with sparkle concerning code signing. So for the time being, I decided that I will remove sparkle as a dependency.</div><div class=""><br class=""></div><div class="">Thanks anyway.</div></div><div class=""><br class=""></div></body></html>