Simon King <simon.k...@uni-jena.de> writes: > Hi Keshav, > > On 2013-03-22, Keshav Kini <keshav.k...@gmail.com> wrote: >> Simon King <simon.k...@uni-jena.de> writes: >>> However, if you *are* upstream (i.e., if your data are only published in >>> this form, but not as an independent project), I'd say tracking it with >>> mercural is fine. But perhaps other people have a different viewpoint. >> >> Please don't. When we merge all the SPKGs' repositories in the git >> transition we don't want to pull in upstream source as well. Feel free >> to just leave it untracked in the src/ directory, like other SPKGs do. > > Perhaps you misunderstood. When I wrote "However, if you *are* > upstream", I really meant that the spkg is the only place in which the > code is published.
Yes, I understood what you meant. > Hence, "we don't want to pull in upstream source as well" simply does not > apply. The question is: Do we want to *remove* source, just because Sage > is the only project that has this code? I would say that yes, we do want to remove it - from the unified repository. The code would still be shipped with Sage in a tarball, but will not be included in the version history of the unified repository. Presumably there's a reason that the hypothetical code in question currently lies in an SPKG and not in the Sage library. In the new directory structure we will be separating the install scripts from the src/ directories, so there won't really be anywhere to put the code from the src/ directories other than in the place where we put other "upstream tarballs". See https://github.com/kini/sage-workflow#directory-structure , or http://wiki.sagemath.org/WorkflowSEP for a more complete picture (subject to change). -Keshav -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
