#3337: [with spkg, needs work] Upgrade gap-guava to new 4.4.12/3.9 release
-------------------------+--------------------------------------------------
 Reporter:  tabbott      |        Owner:  mabshoff
     Type:  enhancement  |       Status:  new     
 Priority:  major        |    Milestone:  sage-3.4
Component:  packages     |   Resolution:          
 Keywords:               |  
-------------------------+--------------------------------------------------
Comment (by wdj):

 I don't know the definition of repo. I assumed it was something which is
 at least part of the sage tree. The old gap spkg is just a tarball I
 downloaded separately. Probably not the main problem here.

 I read both "hg help commit" and "hg help" and don't see how the
 information they provide can be used in this situation. I described the
 process I used to create the spkg in the list above. What I am wondering
 is what step(s) needs to be added/subtracted/modified. When I try
 something like "hg commit" then "hg export", I get this:

 {{{
 w...@hera:~/sagefiles/sagestuff/gap-4.4.12$ hg export
 abort: export requires at least one changeset
 }}
 Obviously that is the wrong idea but it at least follows the process I am
 used to using for Sage code patches. If hg is to be used to create the new
 GAP spkg then obviously (a) I have to learn a lot more and (b) it isn't
 clear to me how to proceed. For example, is "hg remove" to be used for
 every file deleted from the old spkg and "hg add" to be used for every
 file/dir added to the new spkg?

 Maybe all of this should be done inside a copy of Sage and then use
 sage_extcode somehow?

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/3337#comment:14>
Sage <http://sagemath.org/>
Sage - Open Source Mathematical Software: Building the Car Instead of 
Reinventing the Wheel
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to