On Wed, Aug 27, 2014 at 09:35:57 -0400, John W. Eaton wrote: > I explained in a comment to the Octave bug report why I included the file in > the install target and I don't plan to remove it. Is there a better > location for it? Let's deal with whether it's useful at all upstream :) IMHO we already have sufficient means in Debian to see full build logs, check out source snapshots, and reproduce builds in clean chroots. I don't think installing config.log provides any added value to the Debian package and it simply should not be there. But if we were going to keep the file or some equivalent, and ignoring the reproducible build aspect, the main problem for Debian is that it encodes architecture-specific details (e.g. the fact that Octave was built on x86_64) and is installed in an arch:all package, which is supposed to be identical regardless of which system it was built on. So arch:arm64 users should not install octave-common and see the config.log from an x86_64 build, it's meaningless. If we were to keep it, the only place that would make sense would be in the lib directory alongside libraries or oct-files. But I still say nuke it. -- mike
Attachment:
signature.asc
Description: Digital signature