On Sunday, July 21, 2024 1:21:47 PM EDT Wietse Venema via Postfix-users wrote:
> 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?

Thanks,

That's a good question.  I don't know.  I suspect that they are.

In Debian we're focused on reproducibility with the same build environment.  I 
don't think varying things like LANG would be useful to verify the available 
binaries were built from the published source, which is, I as understand it, 
is the primary purpose for reproducible builds.

On a possibly related note, recent versions of man now produce a stack of 
warnings for postconf.f (this is the first one, there are 244, one for each 
line of the man page):

warning: cannot select font 'C' [usr/share/man/man5/postconf.5.gz:1]

As I understand it, the troff variant used that's normally used has never 
supported 'C', but didn't previously raise a warning.  I looked into what font 
should be selected instead and the current answer seems to be don't set a 
font.  Rewrite man pages so it's not needed.  Here's one example:

https://github.com/jgm/pandoc/issues/9020#issuecomment-1692680356

That's the point at which I decided it was more than I cared to think about 
over the weekend.  FYI (and I totally understand you might decide the same on 
a longer term basis).

Scott K


_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org

Reply via email to