Ciao!! Norman Ramsey <[email protected]> wrote: |> There was a missing line continuation in the install: rule of the |> makefile, the fix is on [master]. Thanks so much again! Could it |> be that this fixes your issue? Would be good to know! | |Fixed. | | make OPT_AUTOCC=no VAL_PREFIX=/tmp/s-nail VAL_PRIVSEP_USER=nr install | |Works as expected.
Really?? That is good news! I would not have known where to look at otherwise, easily. And you want me to support CC=cc on the command line, do you? I had it removed already some minutes ago, but i expected many people using CC=cc as a very default, so we would never search for other compilers. But i think OPT_AUTOCC should honour it, finally. Will do. I wonder how VAL_PRIVSEP_USER=nr pays you anything. I have seen the problem arise for the Homebrew recipe that has been recently created, there OPT_DOTLOCK=no was the only (easy) solution for new macOS. We always use normal file locking, even with OPT_DOTLOCK=no, it is just that this is traditionally used, and is used today by default by at least dovecot and OpenBSD smtpd, maybe more. I mean other MUAs do not do it right or care at all anyway (but do not have a security advisory, on the other hand). But if the server uses this when storing data it strives me right to take care of it? And we now follow something similar to the established "config-it && build-it && PRIVILEGED install-it", i would need to add a dependency on config: in install: otherwise, and then the established way of doing things would re-evaluate configuration again, which we definitely do not want. In fact i have changed the build system to this approach because of the careless Debian package, which caused exactly this to happen... Good night! --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt)
