#18710: Move some make targets to build/Makefile
-------------------------------------+-------------------------------------
       Reporter:  jdemeyer           |        Owner:
           Type:  enhancement        |       Status:  needs_review
       Priority:  major              |    Milestone:  sage-6.8
      Component:  build              |   Resolution:
       Keywords:                     |    Merged in:
        Authors:  Jeroen Demeyer     |    Reviewers:
Report Upstream:  N/A                |  Work issues:
         Branch:                     |       Commit:
  u/jdemeyer/move_some_make_targets_to_build_makefile|  
5b6ec50788f2cd19f575adf5f2725d77c4ba6cc3
   Dependencies:  #18533, #18715,    |     Stopgaps:
  #18716                             |
-------------------------------------+-------------------------------------

Comment (by ncohen):

 > There is no difference at all in how `install.log` is treated.

 Be honest for a second Jeroen. There is no difference at all *when make
 build* is called. For all other calls, there is a difference. In these
 situations, it would make more sense to not double-log everything. Why
 don't you move the logging to `install.log` to the `build:` rule in the
 other makefile?

 And then, you can remove the logging from this very very generic rule.

 Nathann

--
Ticket URL: <http://trac.sagemath.org/ticket/18710#comment:29>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-trac+unsubscr...@googlegroups.com.
To post to this group, send email to sage-trac@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.

Reply via email to