#17966: Include the entire boost library
-------------------------------------+-------------------------------------
       Reporter:  slelievre          |        Owner:
           Type:  enhancement        |       Status:  new
       Priority:  major              |    Milestone:  sage-6.9
      Component:  packages:          |   Resolution:
  standard                           |    Merged in:
       Keywords:  boost              |    Reviewers:
        Authors:  fbissey            |  Work issues:
Report Upstream:  N/A                |       Commit:
         Branch:                     |  17822f86318a5cbf5d4f7fa2df19bc8f63c2d099
  u/fbissey/boost_1.59.0             |     Stopgaps:
   Dependencies:                     |
-------------------------------------+-------------------------------------

Comment (by charpent):

 I opened #19570 for a different purpose. François Bissey pointed me to the
 present ticket (which I somehow missed while searching Trac for boost) and
 Jeroen Demeyer closed the ticket.

 I do not understand the issues at hand. As far as I understand, the
 current Sagemath packages husr the boost subdirectory, which is sufficient
 for current Sagemath, whereas, as pointed out by François, various voices
 have spoken in favor of the inclusion of the whole hawg, for goals that do
 not seem overly clear to me.

 As far as I can tell :
 * The original reason of including boost (polybori, a. k. a. brial) is
 fulfilled by the current packaging (headers only).
 * This packaging is no longer stripped from polybori sources, but a
 subdirectory of the original boost tarball.
 * The bits needed by Nathaan Cohen for its graph manipulation purposes
 also are in place.
 * The reasons for packaging the whole hawg are not yet definite plans.
 * This packaging needs significant work.

 So could we split this work in two :
 1. update the current packaging of the headers (that would fix my problemn
 and possibly Nathaans's too).
 2. develop the packaging of the whole boost.

 The packaging of the headers is already a standard package, and therefore
 should probably remain so. The complete libary could become an optional
 package, on which new optional packages could depend.

 However, if some standard package (e. g. ECL) could benefit of the
 inclusion of the whole boost, this library should become standard...

 What do you think ?

--
Ticket URL: <http://trac.sagemath.org/ticket/17966#comment:9>
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 [email protected].
To post to this group, send email to [email protected].
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