Didier has posted a repackaged sage_c_lib (either off-list or on-list -- I 
forget) which adheres to the new spkg format.  This mail is follow-up to that 
to more formally inquire about how to proceed for the sage_c_lib.  I must say 
that I like this new format very much.  It's much clearer what is going on 
upstream and local to sage.

Anyhow, the new package for sage_c_lib gets a bit confusing because we had a 
mercurial repository for the actual development of the sage_c_lib in the 
original sage_c_lib spkg.  The new spkg spec calls for a mercurial repository 
for the spkg-* scripts in the root of the spkg.  Do we want both of these 
mercurial repositories in the spkg?

Here's some options for the purposes of voting on what should happen for the 
sage_c_lib.spkg:
1)  Have a mercurial repository in the root of the spkg for the spkg scripts 
and a *seperate* mercurial repository for development of the actual code in 
the src/ subdirectory (but this separate repository would be kept in the spkg 
as well).
2)  Have a single mercurial repository for both the spkg-* scripts and the 
actual code in the src/ subdirectory.
3)  Keep the actual code source control outside the spkg and release 
non-version controlled tarballs from this to be packaged in the spkg.

I vote for #2.  That seems sad to not make a distinction between 'upstream' 
and spkg-scripts, but the stuff in sage_c_lib currently seems quite unique to 
sage so there is little value to separate them.

Also, does anyone know why there is a squarefree-c_lib.hg file in the spkg?  
It appears to contain patches that were already applied.  I think it should 
be deleted, but I'm not sure and to the I forget the magic command to read hg 
files (What were they smoking to make that binary?!?)

--
Joel

--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---

Reply via email to