Just make the source repository public and cut releases for
p_group_cohomology from that. Even without the change to git I think that
this is a much better model than putting a repo in a tarball and not have
it web accessible.
Since we are already planning on hosting our own git repo for Sage i
Hi Keshav, hi all,
On 2013-03-23, Keshav Kini wrote:
>> 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 i
Simon King writes:
> Hi Keshav,
>
> On 2013-03-22, Keshav Kini wrote:
>> Simon King 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
Hi Keshav,
On 2013-03-22, Keshav Kini wrote:
> Simon King 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.
>
> P
Simon King 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
Christian Stump wrote:
Make a database_foobar.spkg for your tables.
Thanks!
I did that, and everything seems to work (I can install the package
using sage -f cluster_seed-1.0.spkg). Could maybe someone have a look
at it
(http://trac.sagemath.org/sage_trac/raw-attachment/ticket/13425/cluster_s
Hi Christian,
On 2013-03-15, Christian Stump wrote:
>> Make a database_foobar.spkg for your tables.
>
>
> - I initialized the hg repo and added src to the .hgignore. But the
> documentation doesn't say what to do then with it, so this repo is
> still not tracking anything.
IIRC, the idea is that
> Make a database_foobar.spkg for your tables.
Thanks!
I did that, and everything seems to work (I can install the package
using sage -f cluster_seed-1.0.spkg). Could maybe someone have a look
at it
(http://trac.sagemath.org/sage_trac/raw-attachment/ticket/13425/cluster_seed-1.0.spkg)
since I am
