#9433: Put more files under revision control.
----------------------------+-----------------------------------------------
Reporter: jhpalmieri | Owner: tbd
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-4.5.2
Component: distribution | Keywords:
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
----------------------------+-----------------------------------------------
Comment(by ddrake):
In sage-sdist, where you have {{{# copy sage root repo over}}}, why not
just clone the repo? That will take care of copying all the necessary
files, and if we add or remove files tracked by the repo, we won't need to
mess with sage-sdist. I'm thinking that something like
{{{
cd $SAGE_ROOT
hg clone --pull . DEST_DIR
}}}
Using --pull means that it doesn't use hardlinks in the clone; I *think*
there would be no problem with using hardlinks, but it's unlikely to make
a big difference. The clone will include a hgrc file that points to where
it came from: it would look something like this:
{{{
[paths]
default = /home/foo/sage-whatever
}}}
We could simply delete the file, or just leave it, since it would not
negatively affect anything (except running {{{hg pull}}} from SAGE_ROOT,
which you wouldn't do anyway).
So, all the {{{cp -p}}} lines could be just
{{{
hg clone --pull . $TMP
rm $TMP/.hg/hgrc
}}}
and files added or removed to the repo would get copied correctly without
changing any scripts.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9433#comment:12>
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.
