<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><span></span></div><div><meta http-equiv="content-type" content="text/html; charset=utf-8"><div style="-webkit-text-size-adjust: auto;"><span></span></div><div><blockquote type="cite" style="-webkit-text-size-adjust: auto;"><blockquote type="cite"><span>On Aug 16, 2014, at 2:21 PM, René J.V. Bertin <<a href="mailto:rjvbertin@gmail.com">rjvbertin@gmail.com</a>> wrote:</span><br></blockquote></blockquote><blockquote type="cite" style="-webkit-text-size-adjust: auto;"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite" style="-webkit-text-size-adjust: auto;"><blockquote type="cite"><span>On Saturday August 16 2014 13:52:21 Lawrence Velázquez wrote:</span><br></blockquote></blockquote><blockquote type="cite" style="-webkit-text-size-adjust: auto;"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite" style="-webkit-text-size-adjust: auto;"><blockquote type="cite"><span>The blunt answer is no.</span><br></blockquote></blockquote><blockquote type="cite" style="-webkit-text-size-adjust: auto;"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite" style="-webkit-text-size-adjust: auto;"><blockquote type="cite"><span>The nuanced answer is that portfetch does pass "--depth=1" if ${git.branch} is empty, but you'd only be fetching the remote's heads, and we strongly discourage working from heads. (It precludes reproducible builds.)</span><br></blockquote></blockquote><blockquote type="cite" style="-webkit-text-size-adjust: auto;"><span></span><br></blockquote><blockquote type="cite" style="-webkit-text-size-adjust: auto;"><span>What if I want a "daily" port? :)</span><br></blockquote><span style="-webkit-text-size-adjust: auto;"></span><br><span style="-webkit-text-size-adjust: auto;">The problem is that a head can point to one commit on one day and another commit on another day, while ${version} doesn't change. This is why working from heads is not acceptable.</span><br><span style="-webkit-text-size-adjust: auto;"></span><br><span style="-webkit-text-size-adjust: auto;">See clang-3.5, gcc410, and rust for some examples of "snapshot" ports. The best thing to do is to write the port so that it's easy to update from one day to the next.</span><br><span style="-webkit-text-size-adjust: auto;"></span><br><blockquote type="cite" style="-webkit-text-size-adjust: auto;"><span></span></blockquote><blockquote type="cite" style="-webkit-text-size-adjust: auto;"><blockquote type="cite"><span>If your primary concern is development hassle, one workaround is to manually clone the repository somewhere once, then set ${git.url} to its local path while you're developing. Not only do you avoid fetching over the network, Git will simply hardlink the object database instead of using its usual transport</span><br></blockquote></blockquote><blockquote type="cite" style="-webkit-text-size-adjust: auto;"><span></span><br></blockquote><blockquote type="cite" style="-webkit-text-size-adjust: auto;"><span>That's an idea. How does one specify the local path, with a file:// construct?</span><br></blockquote><span style="-webkit-text-size-adjust: auto;"></span><br><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">No, just a normal /path/like/this. A <a href="file:///path/like/this" x-apple-data-detectors="true" x-apple-data-detectors-type="link" x-apple-data-detectors-result="3">file:///path/like/this</a> will work, but Git will revert to using its usual transport — which would still be faster than network fetching, but you'd lose hardlinking. (There are use cases for this, but yours isn't one of them.)</span><br><span style="-webkit-text-size-adjust: auto;"></span><br><span style="-webkit-text-size-adjust: auto;">vq</span><br><span style="-webkit-text-size-adjust: auto;">Sent from my iPhone</span></div></div></body></html>