4 ms·
Also, if you're worried about the occasional regression, you can archive an installer package of the OS X .app (--with-ns) version each time you build by adding
by jasomill 8y ago
Also, if you're worried about the occasional regression, you can archive an installer package of the OS X .app (--with-ns) version each time you build by adding something along the lines of
version="$(date +%Y.%m.%d.%H.%M.%S)"
packagedir="$HOME/Unreliable/Packages"
pkgbuild \
--identifier at.jasomill.pkg.org.gnu.Emacs \
--version "$version" \
--install-location /Applications \
--component nextstep/Emacs.app \
"$packagedir/Emacs-$version.pkg"
to your build script; add
sudo installer -package "$packagedir/Emacs-$version.pkg" -target /
if you also want to install. The resulting package is also a handy way to push the updated version to multiple Macs.
Note, however, that I've reverted to a previous version maybe twice in the past 5+ years of weekly builds (from the GNU master branch), and even in these cases, the regression didn't affect core editing functionality (last one I remember, editing over ssh via tramp was failing in certain circumstances [that I never got around to working out in detail]).