On Dec 22, 6:05 pm, Dan Drake <dr...@kaist.edu> wrote:
> On Mon, 22 Dec 2008 at 10:42AM -0800, mabshoff wrote:
Hi Dan,
<SNIP>
> > Everything but src must be under revision control - unclean repo in
> > the spkg leads to automatic "needs work" from my end at review time
>
> Does that mean src/ must not be under revision control? It would
> certainly be easiest for me to have one hg repo.
If you check out http://wiki.sagemath.org/SPKG_Audit there is a loop
hole, i.e. exceptions are allowed in certain circumstances. So far we
have allowed this if Sage is in effect upstream for a component, i.e.
eclib comes to mind.
> Also, what does "vanilla upstream" mean for SageTeX?
Given its small size I and the fact that Sage seems to be upstream to
SageTeX I would consider it allowed in your case to put either all of
src into the main hg repo or create a second repo inside src for the
code. The second solution is cleaner IMHO. Also note that I forgot to
mention the mandatory .hgignore - which I will be adding to the wiki
in a second.
> Dan
Cheers,
Michael
> --
> --- Dan Drake <dr...@kaist.edu>
> ----- KAIST Department of Mathematical Sciences
> ------- http://mathsci.kaist.ac.kr/~drake
>
> signature.asc
> < 1KViewDownload
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
