#9433: Put more files under revision control.
--------------------------------------------+-------------------------------
Reporter: jhpalmieri | Owner: tbd
Type: enhancement | Status: needs_work
Priority: major | Milestone: sage-4.6.2
Component: distribution | Keywords:
Author: John Palmieri | Upstream: N/A
Reviewer: Leif Leonhardy, Volker Braun | Merged:
Work_issues: |
--------------------------------------------+-------------------------------
Comment(by jhpalmieri):
Replying to [comment:93 jdemeyer]:
> Replying to [comment:92 vbraun]:
> > Replying to [comment:88 jdemeyer]:
> > > Why do we need a {{{sage_root.spkg}}}? I don't see a reason for a
"root repo" to ever exist in tarball form.
> >
> > The way things are set up right now, if you upgrade an existing sage
installation then the updated `SAGE_ROOT_REPO` will merge updates to the
`$SAGE_ROOT` repository. As long as we don't have an official online
repository to pull changes from I don't see any better way to do the
upgrade.
> I have to admit I know nothing about this. If you really think we need
a `sage_root.spkg` then I believe you...
Yes, that's the reason for its existence.
> > I agree that we need to disentangle the `sage_root` repository more
from `sage_scripts`. Basically, everything that `sage_scripts/spkg-
install` manually copies into `$SAGE_ROOT` should be part of the root
repo, like `README.txt`. But I think this can wait until we actually do
have a `sage_root` repository. Then it'll be easy to write complimentary
patches for the two repositories that clean this up.
> Personally, I would rather like to clean this up as part of ''this''
ticket. Keep in mind that adding or changing the working of a SAGE_ROOT
repo will require some changes to the process of merging Sage releases. I
would prefer to have to do this only once, not once for this ticket and
once for every follow-up ticket.
I think I don't understand. Once there is a SAGE_ROOT repo, then any
follow-up ticket can just have a patch which needs to be applied to that
repo, as opposed to manually patching `spkg/install` or `Makefile` or
whatever.
For the particular change you have in mind, it requires modifying various
scripts (like spkg-install, but maybe others?) in local/bin, and it could
possibly be complicated. It seems safer to do things incrementally, first
setting up the new repo, then on a later ticket making further changes.
(I also have a heavy teaching load right now, so I won't have much time to
work on this. I can try to fix bugs with the current implementation when
anyone finds them, but I don't think I can work on any major
modifications, like dealing with the spkg/base repo.)
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9433#comment:94>
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.
