On 11/11/2013 07:22 PM, William Stein wrote:
>> check "git --version" and then don't start trying to build git at all,

> If this (and any other similar) change is made, it needs to be made in
> a way that doesn't mess up the binaries we build.  The binaries that
> are built for generic redistribution should have everything built by
> default.

I guess, it should be standard that a "make" started from a github
checkout tests the system and builds git (or anything else that is
already available in a reasonable version on the system) only if its
non-existing or existing in an incompatible form.

I would assume that for creating the source release one would (instead)
have to type "make dist" [1] and for a binary distribution perhaps "make
bindist". The *result* would then contain/build everything as required.

It's perhaps also reasonable that the Makefile that is produced for the
distribution is slightly different than the one on github or that one
simply adds an additional file to the distribution tarball that enables
"make" to distinguish between github checkout and source/binary
distribution.

Given the many software packages on which Sage builds, I wouldn't expect
that I get exactly the same sage (as in the official release) when I
type "make" from a github checkout. The only thing I would expect is
that I am *able* to build exactly the same distribution files and thus
can do everything localy a release manager usually does. For that, it
is, of course, necessary, to list somewhere the *exact* versions of all
the subpackages that go into a sage release (i.e. to make it reproducible).

I think sage already does the latter with the spkgs, but why not also
have another list for *minimal version requirements* of other software
like git, maxima, ecl, etc.?

Just an idea.

Ralf

[1] http://www.gnu.org/software/make/manual/make.html#Standard-Targets

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

Reply via email to