On Tue, Feb 24, 2015 at 10:02 PM, Chris Bagwell <ch...@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
