#11246: flint-1.5.0.p5's extraneous #includes break typedef ulong in sys/types.h
---------------------------------------------------+------------------------
Reporter: dimpase | Owner: tbd
Type: defect | Status:
positive_review
Priority: major | Milestone:
sage-4.7.2
Component: packages | Keywords: cygwin
Work_issues: | Upstream: N/A
Reviewer: Karl-Dieter Crisman, Leif Leonhardy | Author: Dima
Pasechnik, Jeroen Demeyer
Merged: | Dependencies:
---------------------------------------------------+------------------------
Comment(by dimpase):
Replying to [comment:63 leif]:
> Replying to [comment:49 dimpase]:
> > IMHO, this discussion just highlights a need to revamp the whole spkg
system, for 99% of the standard spkgs, at least.
> > It would be much better if the whole non-building part of the spkg
install is done in a uniform way, by hg, say,
> > rather than handwritten scripts...
> >
> > The need for the current spkg system is dictated by the need of some
optional parts of Sage, that demand, say, a distribution in an unmodified
form. Yet, putting the spkg source under hg is not a modification. Sage
can distribute spkg source with the hg tree, and Sage-needed patches as
patches to be applied by an spkg-install.
>
> If I understand you correctly (having the whole upstream tree under
revision control), that would heavily increase their sizes.
>
Really? Why? If I look at my current $SAGEROOT/devel/sage/, I have 878Mb,
while its .hg is 51Mb. And here the fact that this tree has a long history
must be taken into account. A typical spkg tree would be started from a
clean history, and keep it for most of the files. So it would be a pretty
small increase.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11246#comment:64>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
