Scott Kitterman via Postfix-users:
> Unfortunately, I got distracted from reporting back on this again. Sorting
> AUXLIBS is also needed to make things reproducible:
>
> Index: postfix/makedefs
> ===================================================================
> --- postfix.orig/makedefs
> +++ postfix/makedefs
> @@ -215,7 +215,7 @@ echo "#---------------------------------
> echo "# Start of summary of user-configurable 'make makefiles' options."
> echo "# CCARGS=$CCARGS"
> echo "# AUXLIBS=$AUXLIBS"
> -env | grep '^AUXLIBS_' | sed 's/^/# /'
> +env | grep '^AUXLIBS_' | sed 's/^/# /' | sort
> echo "# shared=$shared"
> echo "# dynamicmaps=$dynamicmaps"
> echo "# pie=$pie"
>
> It would be great if you could apply this in a future release.
This is done. But I'm also trying to be proactive. What differences
should Postfix builds defend against?
For example, the output from 'env' may depend on process history,
so we defend against that by deterministcally sorting the output
(makedefs forces deterministic sort with an LC_ALL=C command).
But Postfix binaries also differ when I change LANG from, say,
en_US.UTF-8 to nl_NL.UTF-8. I see differences in how the compiler
orders (string) constants internally. I would not be surprised if
it also affects how the shell orders filenames as it expands a
wildcard pattern.
Should I worry about LANG/LC_ALL differences, or are those differences
eliminated by the tooling that invokes Postfix build commands?
Wietse
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
