From: Pascal Giard <evilynux@gmail.com>
To: sox developers list <sox-devel@lists.sourceforge.net>
Subject: Re: Reproducible builds and SoX
Date: Thu, 26 Feb 2015 09:05:44 -0500 [thread overview]
Message-ID: <CAJNNDmmQG3TD2OQhKTVb3vfcRH6i6k+HvYYbyS4e_ZhLcMHehQ@mail.gmail.com> (raw)
In-Reply-To: <CAGzDe_bH-Op03nO6Y0Aux+=ShsFB+OMMSrcXOnwSs=QbO51BrQ@mail.gmail.com>
On Tue, Feb 24, 2015 at 10:02 PM, Chris Bagwell <chris@cnpbagwell.com> wrote:
> I've come to not like compile time timestamp showing up in output as well.
> Complicates CI tests checking for behavior regressions, defeats rsync's
> --hard-link option if one uses that to keep backups of past CI builds, etc.
>
> In short term and to prevent breaking our ABI, I suggest changing that field
> to be NULL in both git and patch against debian. sox.c looks for NULL and
> handles gracefully.
Debian is actually frozen until the release of Jessie so I can wait
for the next minor revision.
If that does not come before unstable gets unfrozen, I'll proceed as
you suggest.
> In longer term, I think a better plan is to output something like 'gcc -v'
> outputs; the exact list of options pasted to configure script. That, I
> think, is main intent of these timestamps; simple way to help detect 2
> binaries reporting same version # but compiled with different
> options/behavior.
Sound good. To be continued...
-Pascal
--
Homepage (http://organact.mine.nu)
Debian GNU/Linux (http://www.debian.org)
COMunité/LACIME: École de technologie supérieure (http://www.comunite.ca)
ISIP Laboratory: McGill (http://www.isip.ece.mcgill.ca)
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
SoX-devel mailing list
SoX-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-devel
prev parent reply other threads:[~2015-02-26 14:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-13 18:06 Reproducible builds and SoX Pascal Giard
2015-02-25 3:02 ` Chris Bagwell
2015-02-26 14:05 ` Pascal Giard [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.sourceforge.net/lists/listinfo/sox-devel
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJNNDmmQG3TD2OQhKTVb3vfcRH6i6k+HvYYbyS4e_ZhLcMHehQ@mail.gmail.com \
--to=sox-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/sox.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).