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

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

[Octave-bug-tracker] [bug #37542] consider including doc-cache in the re


From: Mike Miller
Subject: [Octave-bug-tracker] [bug #37542] consider including doc-cache in the release
Date: Thu, 11 Oct 2012 02:55:20 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.92 Safari/537.4

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

                 Summary: consider including doc-cache in the release
                 Project: GNU Octave
            Submitted by: mtmiller
            Submitted on: Wed 10 Oct 2012 10:55:20 PM EDT
                Category: Configuration and Build System
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Feature Request
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: Any

    _______________________________________________________

Details:

Consider including doc/interpreter/doc-cache in the Octave release, i.e. add
to EXTRA_DIST. All other intermediate and end products from building the
documentation are included in the distributed source tree except for this one
file. The only difference I can see in the file from build to build is the
timestamp, username, and hostname on which it was built. Any privacy concerns
there?

The problem I would like to fix here is to be able to build from an official
octave-x.y.z.tar.bz2 release without texinfo or any other tools needed for
building the documentation, but *without* needing to specify --disable-docs to
configure.




    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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