octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #43087] improve support for reproducible build


From: Mike Miller
Subject: [Octave-bug-tracker] [bug #43087] improve support for reproducible builds
Date: Wed, 27 Aug 2014 07:51:23 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/35.0.1916.153 Safari/537.36

URL:
  <http://savannah.gnu.org/bugs/?43087>

                 Summary: improve support for reproducible builds
                 Project: GNU Octave
            Submitted by: mtmiller
            Submitted on: Wed 27 Aug 2014 03:51:22 AM EDT
                Category: Configuration and Build System
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Feature Request
                  Status: None
             Assigned to: mtmiller
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 3.8.2
        Operating System: Any

    _______________________________________________________

Details:

Inspired by a discussion of reproducible builds in Debian (see
https://wiki.debian.org/ReproducibleBuilds), I've looked for and found a few
places in the Octave build system that intentionally encodes variable
information into the build output that depends on time stamps, file paths, and
host-specific information. From a reproducible build perspective, these should
all be removed so that given the same original source, the same result comes
out each time.

Some easy pickings:
* config.log - so bad, why is this now being installed in >= 3.8.1?
* doc-cache - fix the header to just say "created by Octave VERSION" without
any timestamp

Some further/harder changes:
* Timestamps are stored in PDF and PS versions of the manuals
* Timestamps are stored in doc-cache files created when pkgs are installed,
could be solved in pkg similarly to Octave's doc-cache above

There may be others, but these are the obvious ones I've found so far.




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?43087>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]