browsing Sage source code

523 views
Skip to first unread message

William Stein

unread,
Apr 22, 2013, 2:10:51 PM4/22/13
to Harald Schilly, Andrew Ohana, sage-devel
Hi,

There is a link on the sagemath.org web site homepage to the Sage source code (where it says "open source"), and it's to a mercurial repo we self-host (http://hg.sagemath.org/).  I wonder if pointing to 


might be nicer, since github has a much better source code browser in comparison -- it even  has syntax highlighting even (which ours doesn't). 

--
William Stein
Professor of Mathematics
University of Washington
http://wstein.org

Jeroen Demeyer

unread,
Apr 22, 2013, 2:28:16 PM4/22/13
to sage-...@googlegroups.com
On 04/22/2013 08:10 PM, William Stein wrote:
> Hi,
>
> There is a link on the sagemath.org <http://sagemath.org> web site
> homepage to the Sage source code (where it says "open source"), and it's
> to a mercurial repo we self-host (http://hg.sagemath.org/). I wonder if
> pointing to
>
> https://github.com/sagemath/sage
>
> might be nicer, since github has a much better source code browser in
> comparison -- it even has syntax highlighting even (which ours doesn't).
As only link or even the default link, I am against this because the
repo doesn't correspond to Sage. If I would be new to Sage, I would find
it very confusing that the source code repo doesn't correspond to the
downloaded tarball.

Ideally, we should put a link on http://hg.sagemath.org/ but I don't
know how feasible this is.

William Stein

unread,
Apr 22, 2013, 3:37:13 PM4/22/13
to sage-devel@googlegroups.com sage-devel@googlegroups.com


On Apr 22, 2013 11:28 AM, "Jeroen Demeyer" <jdem...@cage.ugent.be> wrote:
>
> On 04/22/2013 08:10 PM, William Stein wrote:
>>
>> Hi,
>>
>> There is a link on the sagemath.org <http://sagemath.org> web site
>>
>> homepage to the Sage source code (where it says "open source"), and it's
>> to a mercurial repo we self-host (http://hg.sagemath.org/).  I wonder if
>> pointing to
>>
>> https://github.com/sagemath/sage
>>
>> might be nicer, since github has a much better source code browser in
>> comparison -- it even  has syntax highlighting even (which ours doesn't).
>
> As only link or even the default link, I am against this because the repo doesn't correspond to Sage. If I would be new to Sage, I would find it very confusing that the source code repo doesn't correspond to the downloaded tarball.
>

We could easily have a github repo that does corr. to the last release.

> Ideally, we should put a link on http://hg.sagemath.org/ but I don't know how feasible this is.
>

> --
> 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+...@googlegroups.com.
> To post to this group, send email to sage-...@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

Keshav Kini

unread,
Apr 23, 2013, 8:57:49 PM4/23/13
to sage-...@googlegroups.com
William Stein <wst...@gmail.com> writes:
> On Apr 22, 2013 11:28 AM, "Jeroen Demeyer" <jdem...@cage.ugent.be> wrote:
>> As only link or even the default link, I am against this because
>> the repo doesn't correspond to Sage. If I would be new to Sage, I
>> would find it very confusing that the source code repo doesn't
>> correspond to the downloaded tarball.
>
> We could easily have a github repo that does corr. to the last
> release.

I think what Jeroen means is that the github repo does not correspond in
directory structure to the current <=sage-5 directory structure found in
the tarballs, complete with SPKGs etc, but rather to the future >=sage-6
directory structure.

-Keshav

Jeroen Demeyer

unread,
Apr 24, 2013, 2:19:28 AM4/24/13
to sage-...@googlegroups.com
Exactly. And moreover, the tool (git vs. hg) doesn't correspond either.

Harald Schilly

unread,
Apr 24, 2013, 6:37:07 AM4/24/13
to William Stein, Andrew Ohana, sage-devel
I'm happy to change this link, I only hesitate because it gives the
wrong impression that we have already switched to git.

H
Reply all
Reply to author
Forward
0 new messages